🐛 Check for well-known CloudInit userdata keys #308
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
v1a1 did not have a Key field to specify the Secret key to find the userdata in so we'd try a few well-known keys. So for just CloudInit check for the existence of those well-known keys as well when checking for a required key in the CloudInit Secret. This fixes TKGs post 5e4469e.
github-actions
bot
added
testing-needed-e2e-fast
size/M
akutz
approved these changes
Dec 14, 2023
Minimum allowed line rate is |
bryanv
added
the
testing-done-e2e-fast
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
v1a1 did not have a Key field to specify the Secret key to find the userdata in so we'd try a few well-known keys. So for just CloudInit check for the existence of those well-known keys as well when checking for a required key in the CloudInit Secret.
This fixes TKGs post 5e4469e.