fix(cmd/provider/main.go): External Secrets Store initialization #66
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.
Description of your changes
Currently, even when command-line flag
--enable-external-secret-stores
is passed to the generated provider, the feature is not enabled.Apparently,
o.Features.Enable(features.EnableAlphaExternalSecretStores)
was missing from the generated code.I also copied how
o.ESSOptions
are initialized from one of AWS providers, otherwise the program would crash.I have:
make reviewable test
to ensure this PR is ready for review.How has this code been tested
I updated
cmd/provider/main.go
file in the provider I'm currently working on, and tested that I can publish connection secrets withspec.publishConnectionDetailsTo
attribute.