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
{{ message }}
This repository has been archived by the owner on Jan 8, 2024. It is now read-only.
I know that it is an enterprise feature of vault, but any thought of adding support for namespaces. They alter the paths slightly and are options that can be passed in the CLI or GUI or API.
The text was updated successfully, but these errors were encountered:
I'll have to look into what it takes to support it. How do you expect this to work? Should namespacing be for gatekeeper as a whole (every request is prefixed with X-Vault-Namespace, or on a mesos task basis (adding a namespace field in the config JSON)?
If a namespace is used then I would do it for every request. That way a gatekeeper can live in it's own namespace completely and be separate from other namespace or the root namespace.
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
I know that it is an enterprise feature of vault, but any thought of adding support for namespaces. They alter the paths slightly and are options that can be passed in the CLI or GUI or API.
The text was updated successfully, but these errors were encountered: