fix(ansible): allow multiple custom secrets without namespaces #5638
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.
Fix a bug where defining multiple custom secrets in an extra-vars file without explicit namespaces would add the default namespace only to the last one, and fail the playbook.
Special notes for your reviewer:
Previously, each iteration of the modified set_fact would overwrite the
seldon_custom_secrets
variable entirely rather than updating it (appending the default namespace to each secret defined incustom_secrets
).