[backport -> release/3.9.x] fix(vault): support array type config reference and multiple nginx subsystem #13953
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.
Automated backport to
release/3.9.x
, triggered by a label in #13855.Original description
Summary
This is a superset of #12672
The PR includes the following fix for vault:
conf_loader
now supports iterate through array-like configuration field and deref the secrets one by one.lua_ssl_trusted_certificate=system, {vault://abc/def}
. This is implemented especially for resty environments that execute the actual kong command, with the optspre_cmd = true
. Vault related functionalities can work normally by using valid partial configuration generated in thepre_cmd
environment. This change does not have a separate changelog entry because it is part of the previous "array-type config vault ref" fix and is more inline with user's intuition.kong_processed_secrets
environment variable/file are now generated by subsystems, so enabling multiple subsystem will generates multiple env var/secret file for storing vault deref result.Checklist
changelog/unreleased/kong
orskip-changelog
label added on PR if changelog is unnecessary. README.mdIssue reference
FTI-6163