Allow reading gitAuthSecret from other secret sources than kubernetes secret #131
Labels
emergent
An issue that was added to the current milestone after planning
kind/enhancement
Improvements or new features
resolution/fixed
This issue was fixed
Milestone
This is a continuation of #122 which was addressed recently via #125.
While it's now possible to read cloud provider credentials or the pulumi access token from various sources, the
gitAuthSecret
is still bound to be a kubernetes secret. This requires operators who want to use services like Vault to use another secret source just for this one secret.I envision this to work the exact same way like
envRefs
have been implemented.The text was updated successfully, but these errors were encountered: