Skip to content
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

ansible-galaxy message ERROR! Invalid collection name should specify reason collection name is invalid #65151

Closed
joelwking opened this issue Nov 21, 2019 · 1 comment · Fixed by #65250
Labels
affects_2.9 This issue/PR affects Ansible v2.9 docs This issue/PR relates to or includes documentation. support:core This issue/PR relates to code supported by the Ansible Engineering Team.

Comments

@joelwking
Copy link

SUMMARY

The written documentation for ansible-galaxy and the error message from the program does not offer the user useful information regarding invalid characters in the collection name.

For example, underscores are permitted in the collection name, but dashes are not.

ISSUE TYPE
  • Documentation Report
COMPONENT NAME

ansible-galaxy

ANSIBLE VERSION
ansible-galaxy 2.9.1
  config file = /home/administrator/ansible/playbooks/ansible.cfg
  configured module search path = [u'/usr/share/ansible', u'/home/administrator/ansible/playbooks/library']
  ansible python module location = /usr/lib/python2.7/dist-packages/ansible
  executable location = /usr/bin/ansible-galaxy
  python version = 2.7.12 (default, Oct  8 2019, 14:14:10) [GCC 5.4.0 20160609]

CONFIGURATION
N/A
OS / ENVIRONMENT

N/A

ADDITIONAL INFORMATION
$ ansible-galaxy collection init joelwking.ansible-mongodb -f
ERROR! Invalid collection name 'joelwking.ansible-mongodb', name must be in the format <namespace>.<collection>.

$ ansible-galaxy collection init joelwking.mongodb -f
- Collection joelwking.mongodb was created successfully
@ansibot
Copy link
Contributor

ansibot commented Nov 21, 2019

Files identified in the description:

If these files are inaccurate, please update the component name section of the description or use the !component bot command.

click here for bot help

@ansibot ansibot added affects_2.9 This issue/PR affects Ansible v2.9 docs This issue/PR relates to or includes documentation. needs_triage Needs a first human triage before being processed. support:core This issue/PR relates to code supported by the Ansible Engineering Team. labels Nov 21, 2019
Akasurde added a commit to Akasurde/ansible that referenced this issue Nov 25, 2019
Akasurde added a commit to Akasurde/ansible that referenced this issue Nov 25, 2019
jborean93 pushed a commit that referenced this issue Nov 26, 2019
Akasurde added a commit to Akasurde/ansible that referenced this issue Nov 26, 2019
…iction

Fixes: ansible#65151

Signed-off-by: Abhijeet Kasurde <[email protected]>
(cherry picked from commit 9dca2bd)
@sivel sivel removed the needs_triage Needs a first human triage before being processed. label Dec 2, 2019
nitzmahone pushed a commit that referenced this issue Dec 4, 2019
…iction (#65276)

Fixes: #65151

Signed-off-by: Abhijeet Kasurde <[email protected]>
(cherry picked from commit 9dca2bd)
D3DeFi pushed a commit to D3DeFi/ansible that referenced this issue Dec 8, 2019
anshulbehl pushed a commit to anshulbehl/ansible that referenced this issue Dec 10, 2019
@ansible ansible locked and limited conversation to collaborators Jan 2, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
affects_2.9 This issue/PR affects Ansible v2.9 docs This issue/PR relates to or includes documentation. support:core This issue/PR relates to code supported by the Ansible Engineering Team.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants