Skip to content
This repository has been archived by the owner on Jan 8, 2024. It is now read-only.

namespace support? #71

Open
kmcvicker opened this issue May 2, 2019 · 2 comments
Open

namespace support? #71

kmcvicker opened this issue May 2, 2019 · 2 comments

Comments

@kmcvicker
Copy link

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.

@nemosupremo
Copy link
Owner

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)?

@kmcvicker
Copy link
Author

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 free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants