add support for subscription activation keys to trusted artifacts #1173
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
…artifacts tasks, including buildah-remoate-oci-ta. It also disables podman subscription-manager integration on all remote builders so that subscripition-manager commands can be used to configure which repos are enabled.
|
basic documentation is here: https://docs.google.com/document/d/1mBCAaIU_4XmvCRoXe-Thg3uIEDAs5yPrWVCx3KPopWY/edit |
|
I guess the changes need to be moved from TA tasks to the PVC based ones. |
|
@rcerven if you are able to help get this in shape to merge, I think it will solve a lot of problems. thanks :) |
chmeliik
reviewed
Jul 18, 2024
rcerven
approved these changes
Jul 18, 2024
chmeliik
approved these changes
Jul 18, 2024
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.
… tasks, including buildah-remoate-oci-ta. It also disables podman subscription-manager integration on all remote builders so that subscription-manager commands can be used to configure which repos are enabled.
i had recently had a couple interactions with people smart about subscription mgmt and they all said that using certs the way we are is wrong and eventually will lead to random build failures due to revoked certs. Activation keys solves that problems, and it solves the problem that Camilla was having in this thread, so I just went ahead and did it.
ref slack thread https://redhat-internal.slack.com/archives/C04PZ7H0VA8/p1721226430548109