Ensure that unencrypted fields during a encryption key rotation are not modified #3215
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.
During a ccdb encryption key rotation unencrypted fields incl. field
updated_at
should not be modified.We've seen cases where
updated_at
&syslog_drain_url
have been modified during rotation. See #3196These changes ensure that only modified fields are updated during a rotation.
While writing the tests we noticed that the droplet table contains the columns
encrypted_environment_variables
andsalt
which are no longer referenced in the droplet model. Thus, it should be save to remove those columns.References:
I have reviewed the contributing guide
I have viewed, signed, and submitted the Contributor License Agreement
I have made this pull request to the
main
branchI have run all the unit tests using
bundle exec rake
I have run CF Acceptance Tests