-
-
Notifications
You must be signed in to change notification settings - Fork 313
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
Add versions to requirements.yml examples #13
Comments
I have gone both ways on this, for the book examples:
That said, it would be kind of nice if Ansible let me say 'override versions and use latest' using the |
@geerlingguy I think a good compromise might be to explicitly put 'version: latest' in the examples and explain in the text that production processes should be locked into specific versions to avoid accidental breakage. |
@aharden Agreed. I think at a minimum I'll do that, and put a 'Warning' aside. Thanks for the suggestion! |
In a production Ansible configuration, it should be a best practice to provide desired versions of Galaxy roles that are to be downloaded to support the playbooks. I recommend adding versions to the roles in the requirements.yml files in the examples as you get closer to the 1.0 release.
The text was updated successfully, but these errors were encountered: