Bump fowlogs_cos_bucket::terraform-ibm-cos from 6.9.0 to 7.3.0

[dependabot]

Bumps fowlogs_cos_bucket::terraform-ibm-cos from 6.9.0 to 7.3.0.

Release notes

Sourced from fowlogs_cos_bucket::terraform-ibm-cos's releases.

v7.3.0

7.3.0 (2024-02-07)

Features

• added support to create a single site bucket using new variable single_site_location* added the ability to set force_delete for bucket deletion* added the ability to set hard_quota (#514) (dc9711e)

v7.2.2

7.2.2 (2024-01-26)

Bug Fixes

• delay before using auth policy which is required as a workaround for this provider issue. NOTE: Upgrades from earlier to version to this version may show a time_sleep.wait_for_authorization_policy being deleted if they are skipping authorisation policy creation. This is expected, since there is no need to delay if the authorisation policy already exists. (#518) (472a353)

v7.2.1

7.2.1 (2024-01-24)

Bug Fixes

• updated variable validation for bucket_configs in fscloud submodule (#507) (122c2cf)

v7.2.0

7.2.0 (2024-01-23)

Features

• add support for the COS module creating a resource key for IAM only, or a resource key for IAM and HMAC.The following input variables are renamed:- create_hmac_key -> create_resource_key- hmac_key_name -> resource_key_name- hmac_key_role -> resource_key_role A new input variable is introduced: generate-hmac-credentialsBy default generate-hmac-credentials is false and an IAM only resource key is created. Change the value to true to generate an IAM and HMAC resource key. Note: This is a change in behavior, previously the default option was to generate an resource key containing both IAM and HMAC keys.When deploying for the first time at this level, everything is deployed as expected on the first apply.When upgrading and requiring the IAM and HMAC resource key, the upgrade sequence should be to two deploys. The first deploy should rename existing properties. Then apply. Then add generate-hmac-credentials = true. Then apply. During the first apply some new terraform_data resources are created, during the second deploy the resource key is upgraded in place.When upgrading and requiring an IAM only resource key, the upgrade sequence may not remove the HMAC key from resource key in the state file; but the IAM key is still present. This will correct itself later, or to force the removal; add generate-hmac-credentials = true. Then apply. Then remove generate-hmac-credentials and apply again. Both applies will be upgrade in place. (#506) (f5db77c)

v7.1.6

7.1.6 (2024-01-20)

Bug Fixes

• deps: update terraform terraform-ibm-modules/cbr/ibm to v1.18.0 (#515) (d9dc9e7)

v7.1.5

7.1.5 (2024-01-17)

Bug Fixes

• made resource_group_id optional, as its only required when create a COs instance (not required for bucket creation). resource_group_id has also been removed as an option in the bucket_configs variable for the buckets submodule. (#513) (4622158)

v7.1.4

7.1.4 (2024-01-02)

... (truncated)

Commits

• dc9711e feat: added support to create a single site bucket using new variable `single...
• 39854bc chore(deps): update ci dependencies (#525)
• 18c50d6 chore(deps): update terraform terraform-ibm-modules/key-protect-all-inclusive...
• 1d60d4c chore(deps): update ci dependencies (#524)
• cb93711 chore(deps): update common-dev-assets digest to f2e1cf2 (#520)
• f624112 chore(deps): update ci dependencies (#519)
• 7ea9c1d chore(deps): update ci dependencies (#516)
• 472a353 fix: delay before using auth policy which is required as a workaround for thi...
• 122c2cf fix: updated variable validation for bucket_configs in fscloud submodule (#...
• f5db77c feat: add support for the COS module creating a resource key for IAM only, or...
• Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)