fix(rds/dbinstance): remove minor engineVersion lateinit #1811
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]>
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
Since the change from #1765, the handling of major and minor engine version is now thoroughly in isUpToDate(). Also the actual
engineVersionis now displayed instatus.atProvider.I noticed that for DBInstance, there was still some code in lateInit(), that also tackled that issue. This results in "unclean" display of the complete engine version also in
forProvidereven when the user only wants to set the major engine version.This can and should now be removed.
Fixes #
I have:
make reviewable testto ensure this PR is ready for review.How has this code been tested
Manually