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

Allow channel names with a forward-slash / in them #580

Open
dhirschfeld opened this issue Dec 28, 2022 · 2 comments
Open

Allow channel names with a forward-slash / in them #580

dhirschfeld opened this issue Dec 28, 2022 · 2 comments

Comments

@dhirschfeld
Copy link
Contributor

When deploying internal conda packages my usual practice has been to namespace channels by their respective team name (which also corresponds to their organisation name in our GitHub Enterprise Server) - e.g. retail/dev, retail/prod

It appears this isn't supported when creating a channel:

raise NotImplementedError(
"We can only handle channel_name/subdir/file.xyz OR"
"channel_name/file.xyz"
)

@dhirschfeld
Copy link
Contributor Author

If I manually populate the database the channel listing appears to work:

image

...but drilling down into any channel fails with the frontend only looking for the first part of the channel name (i.e. channel_name.split('/')[0])

image

image

@dhirschfeld
Copy link
Contributor Author

In my own implementation the namespaces were implemented as physical folders. If the backend storage supports folders that might also be possible in quetz?

Alternatively, I guess the channel name could be url-encoded in the backend... so long as that was transparent to the user
i.e. I'd want the UX to be mamba install -c seau/dev my-package not mamba install seau%2Fdev my-package

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant