Remove NOT NULL constraint from encrypted_kms_key in ar_power_of_attorney_request_resolutions and ar_power_of_attorney_forms #19982
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
…f_attorney_requests_resolutions and ar_power_of_attorney_forms
… encrypted_kms_key
ojbucao
force-pushed
the
remove-kms-null-constraints
branch
from
36ba766 to
e1225f8
Compare
ryan-mcneil
approved these changes
Dec 20, 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.
This PR removes the NOT NULL constraint from the
encrypted_kms_keyfield in thepower_of_attorney_requeststable. This change allows theencrypted_kms_keyfield to accept NULL values.Changes
encrypted_kms_keyfield.schema.rbto reflect the changes in the database schema.