Closed shemau closed 3 weeks ago
The expectation is that this PR will need to skip upgrade test because of the key ring force delete state change. The changes are in example code, not the main module, so no release is required.
/run pipeline
/run pipeline
/run pipeline
/run pipeline
TestRunStandardUpgradeSolution 2024-11-07T10:49:37Z command.go:185: # module.kms[0].module.kms_key_rings["postgresql-key-ring"].ibm_kms_key_rings.key_ring will be updated in-place
TestRunStandardUpgradeSolution 2024-11-07T10:49:37Z command.go:185: ~ resource "ibm_kms_key_rings" "key_ring" {
TestRunStandardUpgradeSolution 2024-11-07T10:49:37Z command.go:185: ~ force_delete = true -> false
TestRunStandardUpgradeSolution 2024-11-07T10:49:37Z command.go:185: id = "postgresql-key-ring:keyRing:crn:v1:bluemix:public:hs-crypto:us-south:a/abac0df06b644a9cabc6e44f55b3880e:e6dce284-e80f-46e1-a3c1-830f7adff7a9::"
TestRunStandardUpgradeSolution 2024-11-07T10:49:37Z command.go:185: # (3 unchanged attributes hidden)
TestRunStandardUpgradeSolution 2024-11-07T10:49:37Z command.go:185: }
This was the only error, so skipping update test.
/run pipeline
:tada: This PR is included in version 3.17.12 :tada:
The release is available on:
v3.17.12
Your semantic-release bot :package::rocket:
Description
Update KMS all inclusive which removes key ring force delete because it is deprecated by the provider
Release required?
x.x.X
)x.X.x
)X.x.x
)Release notes content
Run the pipeline
If the CI pipeline doesn't run when you create the PR, the PR requires a user with GitHub collaborators access to run the pipeline.
Run the CI pipeline when the PR is ready for review and you expect tests to pass. Add a comment to the PR with the following text:
Checklist for reviewers
For mergers