v1.12.7

1.12.7 (2024-09-07)

Bug Fixes

• deps: update terraform ibm to latest for the da solution (#198) (f059237)

v1.12.6

1.12.6 (2024-09-07)

Bug Fixes

• deps: update terraform terraform-ibm-modules/cos/ibm to v8.11.5 (#202) (0d449de)

v1.12.5

1.12.5 (2024-09-07)

Bug Fixes

• deps: update terraform-module (#201) (40c77aa)

v1.12.4

1.12.4 (2024-09-07)

Bug Fixes

• deps: update terraform terraform-ibm-modules/observability-instances/ibm to v2.15.0 (#199) (7390359)

v1.12.3

1.12.3 (2024-09-01)

Bug Fixes

• deps: update terraform terraform-ibm-modules/cos/ibm to v8.11.3 (#197) (a8f7f0e)

v1.12.2

1.12.2 (2024-08-31)

Bug Fixes

• deps: update terraform terraform-ibm-modules/cos/ibm to v8.11.2 (#195) (b65e000)

v1.12.1

1.12.1 (2024-08-31)

Bug Fixes

• deps: update terraform terraform-ibm-modules/cos/ibm to v8.11.1 (#193) (52b808f)

v1.12.0

1.12.0 (2024-08-28)

Features

• updated the default value for skip_cloud_shell_calls to true in the deployable architecture solution. This has been done because the settings can not be set with a service ID or trusted profile currently. If you are using a real user apikey to deploy, you can set the value back to true if you wan't to manage the cloud shell settings using the variable shell_settings_enabled. (#183) (ee8706b)

UPGRADE NOTE: If upgrading from an older release, you will see the destroy of the resource module.account_infrastructure_base.module.account_settings[0].ibm_cloud_shell_account_settings.cloud_shell_account_settings[0]. This is expected, but you can explicitly set the value of skip_cloud_shell_calls back to true if you are using a user apikey to deploy to prevent this destroy.

v1.11.11

1.11.11 (2024-08-25)

Bug Fixes

• deps: update terraform terraform-ibm-modules/cos/ibm to v8.10.7 (#192) (8f57dcb)

v1.11.10

1.11.10 (2024-08-24)

Bug Fixes

• deps: update terraform-module (#189) (015eb4d)