Add schema for profile column in authz2 table #7954
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
force-pushed
the
authz-profile-col
branch
from
8f655fb to
a8b5249
Compare
|
@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. |
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.
Use MariaDB's "instant add column" feature to add a new certificateProfileName column to the existing authz2 table. This column is nullable to reflect the fact that profiles are optional, and to mirror the similarly-added column on the orders table.
This change is standalone, with no code reading or writing this field, so that it can be deployed to production and a follow-up change can begin reading and writing the field all at once with no deployability concerns.
TODO: File a ticket to track deployment of this schema change.
DO NOT MERGE until #7953 has been mergedPart of #7955