fix: stop interacting with GHCR, disable scheduled jobs #48
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
infinitewarp
force-pushed
the
no-more-org-membership
branch
5 times, most recently
from
42325bb to
c9875ef
Compare
infinitewarp
changed the title
infinitewarp
force-pushed
the
no-more-org-membership
branch
from
c9875ef to
78a3bc6
Compare
Pushes to and pulls from GHCR no longer work after 2024-12-09 because the secrets we use are no longer valid. What broke the secrets? They were (still are at the time of this commit) GitHub personal access keys belonging to the user @quipucords-bot, but on 2024-12-09 the @quipucords-bot user was demoted and removed from the org due to newly onerous security restrictions by Red Hat. Until we rewrite this code, probably to use to Quay instead of GHCR, the `reaper` repo will save no new images after PRs merge, and no scheduled jobs will run to reap the AWS and Azure accounts.
infinitewarp
force-pushed
the
no-more-org-membership
branch
from
78a3bc6 to
627383c
Compare
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.
Pushes to and pulls from GHCR no longer work after 2024-12-09 because the secrets we use are no longer valid. What broke the secrets? They were (still are at the time of this commit) GitHub personal access keys belonging to the user @quipucords-bot, but on 2024-12-09 the @quipucords-bot user was demoted and removed from the org due to newly onerous security restrictions by Red Hat.
Until we rewrite this code, probably to use to Quay instead of GHCR, the
reaperrepo will save no new images after PRs merge, and no scheduled jobs will run to reap the AWS and Azure accounts.