ansistrano / rollback Goto Github PK

rollback does not define ansistrano_shared_path variable. Please make all variables available as in deploy project. An idea is to use the same setup.yml.

I think that have need added setup-task.yml like in deploy, because in event before-symlink.yml i cant to get acces to variables ansistrano*. It shows in

What are you think about it?

Using Ansistrano rollback, we can rollback to the last release and with the subsequent rollback we can rollback to the n-1 release. But I want know how to rollback to any specific release directly?

ansible-galaxy install don't install the latest version (master 1.1.1)

ansible-galaxy install carlosbuenosvinos.ansistrano-rollback
....
- downloading role 'ansistrano-rollback', owned by carlosbuenosvinos
- downloading role from https://github.com/ansistrano/rollback/archive/1.1.0.tar.gz
- extracting carlosbuenosvinos.ansistrano-rollback to roles/external/carlosbuenosvinos.ansistrano-rollback
- carlosbuenosvinos.ansistrano-rollback was installed successfully

I think ansistrano-deploy is the same

When using group variables and in the same group are variables for ansistrano.deploy and ansistrano.rollback and we execute ansistrano.rollback role, the role also takes into account the variables of ansistrano.deploy.

For example, we have two variable files for a inventory group:
deploy.yml that has ansistrano_before_symlink_tasks_file and ansistrano_after_symlink_tasks_file variables set
rollback.yml that has ansistrano_rollback_after_symlink_tasks_file set

Why when executing ansistrano.rollback it includes the ansistrano_before_symlink_tasks_file and ansistrano_after_symlink_tasks_file files if are set? It shuldn't be including only the files set in the rollback variables like ansistrano_rollback_after_symlink_tasks_file?

This is causing a deploy when trying a rollback because there is the ansistrano_before_symlink_tasks_file and ansistrano_after_symlink_tasks_file are defined.

Of course we can set the variables directly in the rollback playbook, but it would be interesting to know if there is a way to mantain our variable structure defined by groups.

Thanks a lot!

Can I rollback to previous version without deleting the "bad" release directory? It is useful to keep the directory around in order to further analyse the reason which determined the rollback.

I have a drupal site that I am working on deploying with ansistrano. Drupal is very dependent on the database. I have a deployment that backs up the db the shared directory using the ansistrano_release_version with a -1 appended to the end of the file name.

This will be the name of the release that I want to rollback to and after the rollback I would want to source that database.

Is there an ansistano variable that I can use to get the name of the release that I am rolling back to? Is there a better way of doing this?