fix(declarative): generate correct uuid for transient entities #14082
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.
Summary
Like what was fixed in #13516 , this PR fixed a case in which a valid declarative config(as pasted below) cannot be loaded in dbless mode. (The cert/key are copied from
spec/fixtures/kong_clustering.(crt|key)
pair)The
snis
field with atransient = true
property was added for thecertificates
entity in the PR #13357 . However this has a side effect on thepopulate_ids_for_validation
function when it is being called to generate the nested snis entity under the certificates entity in the declarative config. Without checking thetransient
field, the snis will be regarded as a "parent" to the certificate and the id generation will be skipped.Checklist
changelog/unreleased/kong
orskip-changelog
label added on PR if changelog is unnecessary. README.mdIssue reference
https://konghq.atlassian.net/browse/FTI-6351