Manage bzr branches to deploy files or software.
| parameter | required | default | choices | comments |
|---|---|---|---|---|
| dest | yes | Absolute path of where the branch should be cloned to. |
||
| executable (added in 1.4)
| no | Path to bzr executable to use. If not supplied, the normal mechanism for resolving binary paths will be used. |
||
| force | no | no |
| If yes, any modified files in the working tree will be discarded. Before 1.9 the default value was "yes". |
| name | yes |
SSH or HTTP protocol address of the parent branch. aliases: parent
|
||
| version | no | head | What version of the branch to clone. This can be the bzr revno or revid. |
# Example bzr checkout from Ansible Playbooks - bzr: name=bzr+ssh://foosball.example.org/path/to/branch dest=/srv/checkout version=22
For more information on what this means please read Extras Modules
For help in developing on modules, should you be so inclined, please read Community Information & Contributing, developing_test_pr and Developing Modules.
© 2012–2016 Michael DeHaan
© 2016 Red Hat, Inc.
Licensed under the GNU General Public License version 3.
https://docs.ansible.com/ansible/bzr_module.html