-
Notifications
You must be signed in to change notification settings - Fork 19
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
chore: ansible improvements #254
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM! 👍
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We need to update docker file and probably ansible/requirements
Dockerfile does not need updating because Ansible is installed from pip, which always has the latest versions. Ansible itself will update rapidly (mostly due to rolling release on 3 week schedule to always have up-to-date included community plugins) but ansible-core follows a more conservative release schedule and will warn us through warnings and deprecations for many months/years before failing. Ansible's |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I see. Thank you. Then it looks good to me!
Issue being fixed or feature implemented
Errors and deprecation warnings were being thrown in ansible:
docker_container
community plugin syntaxWhat was done?
How Has This Been Tested?
Tested deploying
devnet-schnapps
with latest Terraform (1.0.5) and Ansible (2.11.4)Breaking Changes
None
Checklist:
For repository code-owners and collaborators only