kola: add --force-flatcar-key flag #398
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
tormath1
force-pushed
the
tormath1/payload
branch
from
1578280
to
ac567ca
Compare
this flag will inject the Flatcar production key to verify the signed payload in the instance to update. It can be useful to verify actual signed payload and not the payload generated by the CI (which uses the development key). It defaults to the current behavior: inject the development key. Signed-off-by: Mathieu Tortuyaux <mtortuyaux@microsoft.com>
Signed-off-by: Mathieu Tortuyaux <mtortuyaux@microsoft.com>
tormath1
force-pushed
the
tormath1/payload
branch
from
ac567ca
to
7c83cb5
Compare
pothos
approved these changes
Dec 1, 2022
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.
this flag will inject the Flatcar production key to verify the signed payload in the instance to update.
It can be useful to verify actual signed payload and not the payload generated by the CI (which uses the development key).
It defaults to the current behavior: inject the development key.
Signed-off-by: Mathieu Tortuyaux mtortuyaux@microsoft.com
Tested with actual payload and testing payload from release servers.