4f20a2f00f
Currently kayobe's ansible galaxy dependencies are unpinned. For versioned roles, any new release will be picked up. For unversioned roles, any new commit to master will be picked up. This is clearly not ideal for stability, and we should pin these dependencies to specific versions to avoid things changing under our feet. For unversioned roles, we may want to consider adding versioning where we have the power to do so. Change-Id: Ib83a0d95b9061b3a57cb0e7c4cff3488ee076664 Story: 2003437 Task: 24633
932 B
932 B
Development
Ansible Galaxy
Kayobe uses a number of Ansible roles hosted on Ansible Galaxy. The
role dependencies are tracked in requirements.yml, and
specify required versions. The process for changing a Galaxy role is as
follows:
- If required, develop changes for the role. This may be done outside of Kayobe, or by modifying the role in place during development. If upstream changes to the role have already been made, this step can be skipped.
- Commit changes to the role, typically via a Github pull request.
- Request that a tagged release of the role be made, or make one if you have the necessary privileges.
- Ensure that automatic imports are configured for the role using e.g. a TravisCI webhook notification, or perform a manual import of the role on Ansible Galaxy.
- Modify the version in
requirements.ymlto match the new release of the role.