-
Notifications
You must be signed in to change notification settings - Fork 3
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
chore(deps): update terraform terraform-ibm-modules/icd-postgresql/ibm to v3.20.3 #619
base: main
Are you sure you want to change the base?
Conversation
/run pipeline |
1b364bb
to
719b18e
Compare
/run pipeline |
719b18e
to
aff3b23
Compare
/run pipeline |
aff3b23
to
9eef463
Compare
/run pipeline |
1 similar comment
/run pipeline |
9eef463
to
b6b54b1
Compare
/run pipeline |
b6b54b1
to
98a5c07
Compare
/run pipeline |
98a5c07
to
bb91fb2
Compare
/run pipeline |
bb91fb2
to
c98835b
Compare
/run pipeline |
c98835b
to
7a03596
Compare
/run pipeline |
TestRunUpgradeExample 2024-12-29T15:34:52Z tests.go:619: Parsing plan output to determine if any resources identified for destroy (PR branch)...
=== NAME TestRunUpgradeExample
terraform.go:236:
Error Trace: /go/pkg/mod/github.com/terraform-ibm-modules/ibmcloud-terratest-wrapper@v1.42.8/testhelper/terraform.go:236
/go/pkg/mod/github.com/terraform-ibm-modules/ibmcloud-terratest-wrapper@v1.42.8/testhelper/tests.go:620
/__w/terraform-ibm-vpe-gateway/terraform-ibm-vpe-gateway/tests/pr_test.go:106
Error: Should be false
Test: TestRunUpgradeExample
Messages: Resource(s) identified to be destroyed
Name: wait_for_authorization_policy
Address: module.postgresql_db.time_sleep.wait_for_authorization_policy[0]
Actions: [delete]
DIFF:
Error getting diff: missing 'before' or 'after' key in JSON
Change Detail:
{
"actions": [
"delete"
],
"after_sensitive": false,
"after_unknown": {},
"before": {
"create_duration": "30s",
"destroy_duration": null,
"id": "2024-12-29T15:17:19Z",
"triggers": null
},
"before_sensitive": {}
} The postgresql used in the advanced example in the upgrade test has changed. Previously the postgresql module always created the timed wait, even when the policy was skipped/not used. The bump to 3.20.0, specifically https://github.com/terraform-ibm-modules/terraform-ibm-icd-postgresql/pull/544/files#diff-dc46acf24afd63ef8c556b77c126ccc6e578bc87e3aa09a931f33d9bf2532fbbR119 made this resource conditional on a policy being created. This is the only change failure in all of the tests, so skipping upgrade test. |
/run pipeline |
This PR contains the following updates:
3.19.16
->3.20.3
Release Notes
terraform-ibm-modules/terraform-ibm-icd-postgresql (terraform-ibm-modules/icd-postgresql/ibm)
v3.20.3
Compare Source
Bug Fixes
v3.20.2
Compare Source
Bug Fixes
v3.20.1
Compare Source
Bug Fixes
v3.20.0
Compare Source
Features
existing_kms_instance_guid
is no longer a supported input. The code will now parse the GUID from the KMS key CRNuse_same_kms_key_for_backups
to give more control over KMS key usagekms_encryption_enabled
has been renamed touse_ibm_owned_encryption_key
fscloud
submodule updates:use_default_backup_encryption_key
anduse_same_kms_key_for_backups
existing_backup_kms_instance_crn
. If you want to use a different KMS key for backups, you can use theexisting_backup_kms_key_crn
input to use an existing key. The DA only supports creating an new key that will be used for both data and backups encryption.ibmcloud_kms_api_key
, and creating a KMS auth policy, that polict will now be scoped to the exact KMS key.(#544) (e2efdc4)
Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.
👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.
This PR has been generated by Renovate Bot.