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

Make secretNamespace optional #1840

Open
p4block opened this issue May 17, 2024 · 0 comments
Open

Make secretNamespace optional #1840

p4block opened this issue May 17, 2024 · 0 comments

Comments

@p4block
Copy link

p4block commented May 17, 2024

Feature description

Make any kind of namespace field in secrets.infisical.com/v? optional

Why would it be useful?

If not stated, both the authentication.secretAuth.credentialsRef.secretNamespace and managedSecretReference.secretNamespace should inherit the namespace of the InfisicalSecret itself

Additional context

As an ArgoCD user, specially after the recent change that requires the token secret to exist in the same namespace as the InfisicalSecret, these values seem to be boilerplate.
I'm not knowledgeable of the specifics and may be missing something, but I think

  • The token secretNamespace no longer serves a purpose after cross-namespace secretrefs were nerfed.
  • The managed secretNamespace with Argo can just be guessed to be == to the Infisical secret namespace for most users.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant