Simplify profile config hashing #8081
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
|
@aarongable, this PR appears to contain configuration and/or SQL schema changes. Please ensure that a corresponding deployment ticket has been filed with the new values. |
aarongable
requested review from
jprenken and
beautifulentropy
and removed request for
jsha
aarongable
force-pushed
the
rm-old-profile-config
branch
2 times, most recently
from
54c377b to
8a6c669
Compare
aarongable
force-pushed
the
rm-old-profile-config
branch
from
8a6c669 to
3fa3184
Compare
jprenken
approved these changes
Mar 26, 2025
beautifulentropy
approved these changes
Mar 26, 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.
Remove the backwards-compatible profile hashing code. It is no longer necessary, since all deployed profile configs now set IncludeCRLDistributionPoints to true and set the UnsplitIssuance flag to true. Catch up the CA and crl-updater configs to match config-next and what is actively deployed in prod.
Part of #8039
Part of #8059
The corresponding production config changes were made in IN-11009 and IN-11048