fix(deps): update terraform terraform-ibm-modules/trusted-profile/ibm to v3

[terraform-ibm-modules-ops]

This PR contains the following updates:

Package	Type	Update	Change
terraform-ibm-modules/trusted-profile/ibm (source)	module	major	2.2.0 -> 3.0.0

---

Release Notes

terraform-ibm-modules/terraform-ibm-trusted-profile (terraform-ibm-modules/trusted-profile/ibm)

v3.0.0

Compare Source

(#​181) (07e3a80)

Bug Fixes

• added a fix to prevent resources getting destroyed when a trusted profile name is being renamed
  • trusted_profile_policies now has a required attribute called unique_identifier which must have a unique value per policy. It is only used by terraform for building map objects, it is not use for any actual resource naming. Changing this value will cause resources to be recreated.
  • trusted_profile_claim_rules now has a required attribute called unique_identifier which must have a unique value per claim rule. It is only used by terraform for building map objects, it is not use for any actual resource naming. Changing this value will cause resources to be recreated.
  • trusted_profile_links now has a required attribute calledunique_identifier` which must have a unique value per profile link. It is only used by terraform for building map objects, it is not use for any actual resource naming. Changing this value will cause resources to be recreated.

BREAKING CHANGES

• If upgrading from a previous version, you can prevent resources from being recreated if you use the correct value for the new unique_identifier attribute. For example, if you used the following value for trusted profile name: trusted_profile_name = "my-profile" you should use the following naming conventions:

Trusted profile policies

trusted_profile_policies = [
    {
      unique_identifier = "my-profile-0" # use the format of "<trusted profile name>-0" for first item in the list
      ...
      ...
    },
    {
      unique_identifier = "my-profile-1" # use the format of "<trusted profile name>-1" for second item in the list, and so on
      ...
      ...
    }
]

Trusted profile policies

trusted_profile_claim_rules = [
    {
      unique_identifier = "my-profile-0" # use the format of "<trusted profile name>-0" for first item in the list
      ...
      ...
    },
    {
      unique_identifier = "my-profile-1" # use the format of "<trusted profile name>-1" for second item in the list, and so on
      ...
      ...
    }
]

Trusted profile links

trusted_profile_links = [
    {
      unique_identifier = "my-profile-0" # use the format of "<trusted profile name>-0" for first item in the list
      ...
      ...
    },
    {
      unique_identifier = "my-profile-1" # use the format of "<trusted profile name>-1" for second item in the list, and so on
      ...
      ...
    }
]

v2.3.1

Compare Source

Bug Fixes

• removed the link validation and updated the module to only pass name if cr_type is not 'IKS_SA' or 'ROKS_SA' (#​180) (ca23b79)

v2.3.0

Compare Source

Features

• improved user experience for validating input variable values
  * updated required terraform to be >= 1.9.0 (#​162) (1a72bc6)

---

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.

---

• If you want to rebase/retry this PR, check this box

---

This PR has been generated by Renovate Bot.

[terraform-ibm-modules-dev]

/run pipeline

[terraform-ibm-modules-ops]

🎉 This PR is included in version 1.6.1 🎉

The release is available on:

• GitHub release
• v1.6.1

Your semantic-release bot 📦🚀