feat(getConfig): add vault credentials to already fetch secrets #5604
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
Using the
getConfigstep as part of theSAP/project-piper-actionto retrieve the step configuration for an (enterprise) step:does not resolve vault credentials since the invocation of the Vault client within
GetStepConfig(see here) will be skipped since the Vault credentials aren't set.Usually, setting the Vault credentials is done within the
PrepareConfigfunction within each_generated.gofile but thegetConfigstep does not have such a file. Therefore, we need to add this logic here as well.We are open for any discussions about other ways to achieve our goal. Feel free to reach out.
Checklist