Remove version key from role metadata #82
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Ansible 2.0 seems to have gotten stricter with its parsing of role metadata. It's bombing on the `version` key in this role. ``` ERROR! 'version' is not a valid attribute for a RoleMetadata The error appears to have been in 'roles/davidwittman.redis-1.0.6/meta/main.yml': line 2, column 1, but may be elsewhere in the file depending on the exact syntax problem. ``` Remove the key and all is well again in Ansible 2.0 land.
|
Thanks for the PR @davekonopka. Are you getting this error when installing via |
|
Related: ansible/ansible#13496 |
DavidWittman
added a commit
that referenced
this pull request
Dec 10, 2015
Remove version key from role metadata
|
Thanks for taking a look at this and linking the Ansible issue. I wasn't aware of the version string being a workaround for ansible librarian. I've run into that very interdependency issue so I'm eager to see if this gets addressed upstream. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Ansible 2.0 seems to have gotten stricter with its parsing of role metadata. It's bombing on the
versionkey in this role.Remove the key and all is well again in Ansible 2.0 land.