-
Notifications
You must be signed in to change notification settings - Fork 54
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
terraform-provider: require kubernetes and microservice version #2791
Conversation
✅ Deploy Preview for constellation-docs canceled.
|
875f97d
to
fc262e2
Compare
fc262e2
to
8fcdccb
Compare
494472c
to
958781c
Compare
Running E2E |
958781c
to
b5b684b
Compare
Coverage report
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM except for the one comment
name = "constell" | ||
version = "vX.Y.Z" | ||
kubernetes_version = "vX.Y.Z" | ||
microservice_version = "vX.Y.Z" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
shouldn't this be equal to version
and thus obsolete?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
no. version refers to the image_version is and is renamed to make this more clear in #2775
Context
The provider is currently using a default when no version is specified for these fields. This however leads to an unexpected upgrade state, because new versions defaults, as part of provider upgrades, are not seen as state change by Terraform. Consequently, the new defaults are not applied. This is especially undesired for the microservice version, which should always coincide with the provider version.
Proposed change(s)
breaking change
to make users awareAdditional info
Checklist