10-07-2018 | Remy van Elst
This callback plugin creates a VCS branch every time you run Ansible. If you ever need to go back to a certain state or environment, check out that branch and be sure nothing has changed.
This is useful when you have multiple environments or multiple people deploying and continually develop your Ansible. When you often deploy to test / acceptance and less often to production, you can checkout the last branch that deployed to production if a hotfix or other maintenance is required, without having to search back in your commits and logs. I would recommend to develop infrastructure features in feature branches and have the master branch always deployable to production. However, reality learns that that is not always the case and this is a nice automatic way to have a fallback.
The plugin requires 'GitPython'. On Ubuntu this can be installed with the package manager:
apt-get install python-git python3-git
The plugin requires the Ansible folder to be a git repository. If you have a seperate 'roles' directory, that is not included in this plugin.
The plugin is hosted on Github: https://github.com/RaymiiOrg/log_vcs
To install the plugin, create a folder in your Ansible folder:
mkdir -p plugins/callbacks
Place the file in there and edit your
[defaults] callback_whitelist = log_vcs callback_plugins = plugins/callbacks
If you have multiple environments (multiple inventories) then every inventory needs a
environment. The plugin uses this in the branch name. In my case it can be
mgmt. It is not required, if it is not found the plugin will substitute it with
The branch name format is:
There is no auto-commit or auto-push to a git server. In my use-case deployment is always done from a management machine, otherwise you have to extend the plugin to do auto-commit and push. I decided in my case it would not be useful.
Auto-cleanup is also not implemented. We have bash for that:
git branch | grep 'auto-' | xargs -L 1 -I % git branch -d %