fix: revert type of status.upgradedPostgresVersion to string#1745
Merged
rooftopcellist merged 1 commit intoansible:develfrom Mar 4, 2024
Merged
fix: revert type of status.upgradedPostgresVersion to string#1745rooftopcellist merged 1 commit intoansible:develfrom
rooftopcellist merged 1 commit intoansible:develfrom
Conversation
rooftopcellist
approved these changes
Mar 4, 2024
This file contains hidden or 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
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.
SUMMARY
Closes #1738
As follow-up for #1741, this PR changes to store
status.upgradedPostgresVersionas astring, to keep backward compatibility.ISSUE TYPE
ADDITIONAL INFORMATION
Tested by following reproducible steps in #1738 (comment).
In step 7, deploy customized Operator with this PR instead of
develimage:In step 8, I can confirm there is no
failedtask.In step 10. I can confirm PSQL 15 is running.
In step 11, the
statushasupgradedPostgresVersion.In addition, just to be sure, I restarted Operator to trigger new reconciliation loop for existing AWX that has
upgradedPostgresVersionand verified that the loop completes without any errors.