org level custom secret manager connector cannot use project level secrets
under review
P
Polite Manatee
We have created a custom secret manager to be used by our projects. I wanted to define this at the Org level so that it can be used by all the projects, but Access to the related secrets are project specific, so we need to use project level secrets for the segregation.
The system says that this is not allowed.
Should this not be our choice?
I want to define the connector once. I see this like a defined procedure that the projects can call. Instead we are forced to define the connector within each project. I don't understand the restriction which Harness have put in place.
Why can't we use project level resources with an org defined connector?
Log In
A
Abhishek Thamman
Hi Polite Manatee,
Thanks for your request. It is possible today to create a secret at the project scope using a secret manager connector at the org/account scope. Please refer to the attached screenshot. Let me know if you are facing any issues or would like to chat about this.
Best,
Abhishek Thamman
Prateek Mittal
under review