Can't create a collection with namespace if folder with namespace already exists

[yemi-kelani]

Bug Report

What did you do?

I created a collection callednamewith a namespace callednamespace. Then I tried to create a second collection with the same namespace (namespace`).

What did you expect to see?

It should create the second collection in the same folder.

What did you see instead? Under which circumstances?

The attempt to create the second collection failed. The core command `ansible-galaxy collection init COLLECTION_NAME.COLLECTION_NAMESPACE' seems to be the blame...

[!NOTE]
See Additional comments on issue.

Possible Solutions

• It might be possible to handle this in the operator-sdk repo
• Bar the user from creating collections in this circumstance or warn them
• Create a bandaid solution that detects if the namespace folder exists, determines its current state as a collection or not , etc., creates an alternate uuid for the namespace behind the scenes so the command doesn't fail, then replaces all appropriate values with the proper namespace. This is a large workaround...

Additional context

The namespace is tied to multiple values in the collection like the domain and namsespace fields in the galaxy and operator-config files.

[yemi-kelani]

[!NOTE]
This was my user error. The command takes COLLECTION_NAMESPACE.COLLECTION_NAME as input and I had it reversed. My mistake.