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

Importing and exporting namespaces only available with key not with namespace name #3352

Open
camxus opened this issue Aug 5, 2024 · 2 comments

Comments

@camxus
Copy link

camxus commented Aug 5, 2024

type Document struct {

Description:

Currently, the import and export functionality for namespaces only supports using keys for namespace operations.

Current Behavior:

The namespace parameter for import/export operations accepts only string values representing the key.
This string value is used for both the key and the name, which can be restrictive if a namespace's key and name are different.

Expected Behavior:

The namespace parameter should support using the name of the namespace directly for import/export operations.
This change would allow users to specify a namespace by its name.

@GeorgeMac
Copy link
Member

@markphelps should be covering this in #3356 👍

We're going to make space for description too. Thanks for raising this!

@GeorgeMac
Copy link
Member

Ah sorry @camxus I misinterpretted what Mark was fixing and your request.
Mark is fixing the fact that our declarative format does not support the ability to add description or name.

Just to clarify, you want to be able to export or import using name instead of key (as in via --namespace)?

The fiddly part is that we don't enforce uniqueness on name. It mostly just a readable label.
The key is the unique and immutable reference for these resources (flag / segment / namespace).

This makes that option a bit tricky to use, since you could end up importing into multiple, or exporting from multiple, if they each have the same name. Maybe that is or is not problematic, I am not sure.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
Status: No status
Development

No branches or pull requests

3 participants