Vmc gi version tag#46589
Conversation
Community GuidelinesThis comment is added to every new Pull Request to provide quick reference to how the Terraform AWS Provider is maintained. Please review the information below, and thank you for contributing to the community that keeps the provider thriving! 🚀 Voting for Prioritization
Pull Request Authors
|
|
Co-authored-by: Jared Baker <jar-b@users.noreply.github.com>
Co-authored-by: Jared Baker <jar-b@users.noreply.github.com>
Co-authored-by: Jared Baker <jar-b@users.noreply.github.com>
Co-authored-by: Jared Baker <jar-b@users.noreply.github.com>
Co-authored-by: Jared Baker <jar-b@users.noreply.github.com>
Co-authored-by: Jared Baker <jar-b@users.noreply.github.com>
|
Thanks for your contribution, @ab-cs13! 👍 |
|
Warning This Issue has been closed, meaning that any additional comments are much easier for the maintainers to miss. Please assume that the maintainers will not see them. Ongoing conversations amongst community members are welcome, however, the issue will be locked after 30 days. Moving conversations to another venue, such as the AWS Provider forum, is recommended. If you have additional concerns, please open a new issue, referencing this one where needed. |
Rollback Plan
If a change needs to be reverted, we will publish an updated version of the library.
Changes to Security Controls
NA
Description
gi_version is a mandatory field when creating a cloud_vm_cluster. The underlying API accepts only the major gi_version values 19.0.0.0 or 23.0.0.0, or a value sourced from the list-gi-versions data source.
After creation, the cloud-vm-cluster read operation returns the full GI version (for example, 23.1.4.0.5). In Terraform, this is stored in the computed_gi_version attribute. We then derive the major GI version by parsing the major portion (e.g., 23.1.4.0.5 → 23.0.0.0).
Recently, the underlying API introduced a change that is not compatible with the current parsing logic. Specifically, for the major version 26.0.0.0, the read operation returns 23.1.2.5, which causes Terraform to fail.
This PR introduces a tag-based approach to preserve the user-provided major gi_version input.
References
Output from Acceptance Testing