fix(dbinstance): remove DeleteAutomatedBackups from isUpToDate-check #1750
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
Signed-off-by: Charel Baum (external expert on behalf of DB Netz AG) <[email protected]>
haarchri
approved these changes
May 4, 2023
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.
Description of your changes
The parameter
DeleteAutomatedBackupscauses an update-loop, if set (true or false) in the claim.This change adds it to the ignored fields in
isUpToDate. The parameter is only relevant on delete. (AWS delete-db-instance)Also small change: there is no need to run through
isUpToDatewhile the DB is indeletingstate/status.I have:
make reviewable testto ensure this PR is ready for review.How has this code been tested
Manually with db-instance example