You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
The text was updated successfully, but these errors were encountered:
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.
flipt/internal/ext/common.go
Line 8 in 5a9637d
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.
The text was updated successfully, but these errors were encountered: