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

add namespace limitations #2308

Open
wants to merge 1 commit into
base: devel
Choose a base branch
from
Open

Conversation

samccann
Copy link
Contributor

The content had a 404 and doesn't appear to exist in the galaxy ng docs so pulling those details back into these requirements docs so we don't lose the info.

@samccann samccann requested a review from a team as a code owner December 20, 2024 17:58
@ansible-documentation-bot ansible-documentation-bot bot added the sc_approval This PR requires approval from the Ansible Community Steering Committee label Dec 20, 2024
Comment on lines +304 to +305
* Namespace names in Galaxy are limited to lowercase word characters (a-z, 0-9) and '_', must have a minimum length of 2
characters, and cannot start with an '_'. No other characters are allowed, including '.', '-', and space.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
* Namespace names in Galaxy are limited to lowercase word characters (a-z, 0-9) and '_', must have a minimum length of 2
characters, and cannot start with an '_'. No other characters are allowed, including '.', '-', and space.
* Namespace names in Galaxy are limited to lowercase word characters (a-z, 0-9) and '_', must have a minimum length of 2 characters, and cannot start with an '_'. No other characters are allowed, including '.', '-', and space.

@Andersson007
Copy link
Contributor

So we don't have any doc stating this at the time being? I think we should also open an issue against Galaxy NG to but that page back or maybe open a PR against https://ansible.readthedocs.io/projects/galaxy-ng/en/latest/community/userguide/ and once it's merged refer to it from here, thoughts? Anyway, I'm OK with merging this PR.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
sc_approval This PR requires approval from the Ansible Community Steering Committee
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants