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

Create namespace shaunsund-ansible and bluepants-dev #3355

Open
shaunsund opened this issue Apr 26, 2024 · 12 comments
Open

Create namespace shaunsund-ansible and bluepants-dev #3355

shaunsund opened this issue Apr 26, 2024 · 12 comments
Assignees
Labels
area/namespace Request for a new namespace

Comments

@shaunsund
Copy link

shaunsund commented Apr 26, 2024

Namespace Request

Namespace: shaunsund-ansible and bluepants-dev

Description

shaunsund-ansible
Ansible roles/collections from shaunsund
bluepants-dev
Ansible roles/collections from bluepants.dev

GitHub Org Link

https://github.com/shaunsund-ansible
https://github.com/bluepants-dev

Admins

shaunsund

@shaunsund shaunsund added the area/namespace Request for a new namespace label Apr 26, 2024
@traytorous
Copy link

@shaunsund namespace names cannot have "-" in the names. Also are you asking for two different namespaces.

@shaunsund
Copy link
Author

@traytorous My bad, let's go with "bluepants_dev". Are 2 namespaces not allowed in an issue? or overall?

@traytorous
Copy link

@shaunsund here is the namespace -> https://galaxy.ansible.com/ui/namespaces/bluepants_dev/ . Two namespaces are allowed I just wanted to make sure that it is what you wanted. Would you like for me to create a namespace called "shaunsund_ansible". And what is "shaunsund_ansible" woud be used for.

@shaunsund
Copy link
Author

shaunsund commented May 1, 2024

@traytorous Thank you for the "bluepants_dev" namespace. Please create the "shaunsund_ansible" namespace, it'll be for WIP and random items.

@shaunsund
Copy link
Author

shaunsund commented May 1, 2024

Do I have this right? The URL it is trying to import gives a 404 because of the " _ ". Github doesn't allow " _ ", yet in galaxy you can't have "-".
Screenshot 2024-05-01 at 5 45 04 PM

Looking closer, it appears Role namespaces can have "-" while Collection namespaces cannot - only "_".

So, if I am correct, let's go with "bluepants_dev" for the Collection namespace and "bluepants-dev" for the Role namespace.
And similar for the "shaunsund_ansible". Collection: "shaunsund_ansible" and "shaunsund-ansible" for the Role.

Again, let me know if I have this correct.

@shaunsund
Copy link
Author

@traytorous One more question, it seems github is the only source allowed, is there not a way to specify a custom repo to import from?

@shaunsund
Copy link
Author

@traytorous I found some answers using the command line ansible-galaxy role import --api-key <key> <namespace> <repopname> from my git repo. I guess the Web UI is still under construction.

For the record, I was getting

  File "/venv/lib64/python3.11/site-packages/pulpcore/tasking/tasks.py", line 66, in _execute_task
    result = func(*args, **kwargs)
             ^^^^^^^^^^^^^^^^^^^^^
  File "/app/galaxy_ng/app/api/v1/tasks.py", line 478, in legacy_role_import
    raise Exception('permission denied')

when trying my default namespace. Using the command line was the work around.

As for the renaming I mentioned above, I can work with this, but I would be thankful if they were renamed.

@traytorous
Copy link

Good evening,
I apologize for the late response. We are currently trying to debug an issue in our systems related to this request. A bug ticket has been opened and we are waiting on more information. I will update you once I have more information.

@shaunsund
Copy link
Author

Thanks for the update!

@shaunsund
Copy link
Author

@traytorous Just looking for an update on this. In the meantime, would it be possible to have 'bluepantsdev' created for both Collection and role namespaces?

@traytorous
Copy link

Hello @shaunsund . Please check here -> https://galaxy.ansible.com/ui/namespaces/bluepantsdev/

@shaunsund
Copy link
Author

@traytorous Great! Thank you! Hopefully you can resolve that issue soon, but this lets me move forward.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/namespace Request for a new namespace
Projects
None yet
Development

No branches or pull requests

5 participants