I was trying to export my own Namespace with containing . (dots) in it over web-gui.
Example: My.Namespace
It throws an 404 immediately.
However removing the dot (MyNamespace) and saving solves this issue.
Maybe related to this post?
I don’t think it is but it is an unfortunate edge case I didn’t think of, unfortunately.
If you can get around it by not using dots in your namespace, do that for now, please.
I’ll open up a ticket to address this in some future patch release.
2 Likes
This now should be fixed. I tried testing it and it is working as expected.
1 Like
Verified and working.
Just a quick follow up to mention that in the context of calling apps “Namespaces” it makes a lot of sense to allow for “dots” in the name.
It is my understanding that something along the lines of marketplaces are in the roadmap so naming one’s apps as a subdomain under one’s domain (thus generating a FQD) makes it a natural fit.
Let me clear things up, we allow “.” in names, but since exporting is via API and query parameters we have to URI encode the params(name, slug). That was the only thing fixed/changed
1 Like