feat: extend external secrets support to mssql subchart #475
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The main Octopus chart already supports external secrets via the createSecrets flag - this PR adds the same capability to the MSSQL subchart.
Currently, users wanting to use external secrets management can do so for the main Octopus application secrets, but the MSSQL subchart always creates its own internal secret for the sa user. This creates inconsistency and prevents full external secrets management.