You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm new to working on collections. I've mostly written local-only plugins/modules and roles in the past. I noticed that if I reference my collection in a role meta/main.yml file, I get a schema error from ansible-lint because my namespace name has a number in it.
Is there a reason that I'm not aware of that namespaces in the schema are limited to alphabet characters only? Is this a difference between the ansible-lint schema and requirements of ansible-galaxy or is there a reason why I should not use a namespace with a number in it?
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
Hello.
I'm new to working on collections. I've mostly written local-only plugins/modules and roles in the past. I noticed that if I reference my collection in a role meta/main.yml file, I get a schema error from ansible-lint because my namespace name has a number in it.
Is there a reason that I'm not aware of that namespaces in the schema are limited to alphabet characters only? Is this a difference between the ansible-lint schema and requirements of ansible-galaxy or is there a reason why I should not use a namespace with a number in it?
Beta Was this translation helpful? Give feedback.
All reactions