Skip to content

Releases: terraform-ibm-modules/terraform-ibm-trusted-profile

v3.1.1

12 Jun 08:43
v3.1.1
4baead8

Choose a tag to compare

3.1.1 (2025-06-12)

Bug Fixes

  • deps: update required ibm provider version to >= 1.79.1, < 2.0.0 (#193) (4baead8)

v3.1.0

29 May 18:42
v3.1.0
d0f234e

Choose a tag to compare

3.1.0 (2025-05-29)

Features

  • Updates to trusted-profile-template submodule:
    - identity_crn input has been changed to identities and now supports all identitiy types: user, serviceid and crn. Its also now optional to pass any idenitify.
    - Added support to assign trusted profile template to single accounts using new input account_ids_to_assign (#189) (d0f234e)

v3.0.0

19 May 10:33
v3.0.0
07e3a80

Choose a tag to compare

3.0.0 (2025-05-19)

(#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

15 May 07:15
v2.3.1
ca23b79

Choose a tag to compare

2.3.1 (2025-05-15)

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

05 May 08:28
v2.3.0
1a72bc6

Choose a tag to compare

2.3.0 (2025-05-05)

Features

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

v2.2.0

02 May 19:17
v2.2.0
81943a2

Choose a tag to compare

2.2.0 (2025-05-02)

Features

  • Changed the policy_templates schema to allow user to choose exact attributes
  • Removed the boolean onboard_all_account_groups and replaced it with account_group_ids_to_assign which allows consumers to pass a list of account IDs (or pass "all" for all account groups)
  • Added workaround for IBM terraform provider bugs: #6216, #6214, #6213

(#171) (81943a2)

v2.1.1

18 Apr 11:24
v2.1.1
01948e0

Choose a tag to compare

2.1.1 (2025-04-18)

Bug Fixes

  • add fix to the format of iam_id used in trusted profile template submodule (#166) (01948e0)

v2.1.0

17 Apr 12:03
v2.1.0
eb7dfe6

Choose a tag to compare

2.1.0 (2025-04-17)

Features

  • added support to the root level module to set a trust idenitity using new input trusted_profile_identity
    - added a new trusted-profile-template submodule. For example usage, see the following example. (#159) (eb7dfe6)

v2.0.1

11 Mar 15:22
v2.0.1
860299c

Choose a tag to compare

2.0.1 (2025-03-11)

Bug Fixes

  • deps: update the minimum required ibm provider version (#142) (860299c)

v2.0.0

06 Feb 05:50
v2.0.0
1246388

Choose a tag to compare

2.0.0 (2025-02-06)

Features

  • add support for creating multiple trusted profile links in a single trusted profile (#129) (1246388)

BREAKING CHANGES

  • If upgrading from previous version, terraform would flag the trusted-profile links to be recreated. To prevent the recreation of the trusted-profile links run the following command.
terraform state mv 'module.trusted_profile.ibm_iam_trusted_profile_link.link["<trusted-profile-name>-0"]' 'module.trusted_profile.ibm_iam_trusted_profile_link.link["<trusted-profile-name>-0-0"]'