Flush transitive aliases during deployment [RHELDST-28321] #764
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
amcmahon-rh
requested review from
rohanpm,
negillett and
crungehottman
as code owners
amcmahon-rh
force-pushed
the
RHELDST-28321
branch
from
ec42f5a to
5b72e79
Compare
rohanpm
previously approved these changes
Jan 6, 2025
We saw some repo instability after a recent GA. This was due to only a portion of affected URLs being flushed. The current deployment cache flush only gets URLs based on directly updated aliases. This didn't take into consideration URLs that require several aliases to be applied.
amcmahon-rh
force-pushed
the
RHELDST-28321
branch
from
5edd937 to
6e6747a
Compare
for more information, see https://pre-commit.ci
negillett
approved these changes
Jan 6, 2025
rohanpm
approved these changes
Jan 6, 2025
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.
We saw some repo instability after a recent GA. This was due to only a portion of affected URLs being flushed. The current deployment cache flush only gets URLs based on directly updated aliases. This didn't take into consideration URLs that require several aliases to be applied.