chore(deps): update terraform-module

[terraform-ibm-modules-ops]

This PR contains the following updates:

Package	Type	Update	Change
github.com/terraform-ibm-modules/terraform-ibm-powervs-instance	module	minor	v0.2.6 -> v0.3.0
terraform-ibm-modules/landing-zone/ibm (source)	module	minor	4.4.6 -> 4.6.0

---

Release Notes

terraform-ibm-modules/terraform-ibm-powervs-instance (github.com/terraform-ibm-modules/terraform-ibm-powervs-instance)

v0.3.0

Compare Source

Features

• update os registration for PER DC (#​93) (376f426)

v0.2.8

Compare Source

Bug Fixes

• support dal10 dc (#​88) (6220f11)

v0.2.7

Compare Source

Bug Fixes

• update ansible version to 1.1.3 (#​86) (313c240)

terraform-ibm-modules/terraform-ibm-landing-zone (terraform-ibm-modules/landing-zone/ibm)

v4.6.0

Compare Source

Features

• Add OCP boot volume KMS encryption support (NOTE: Enabled by default for new clusters, but will not be enabled when upgrading from previous version as encryption can only occur at initial provision time) (#​534) (26f0d20)

v4.5.5

Compare Source

Bug Fixes

• update required ibm provider version to >= 1.56.1 (#​545) (39f1a6f)

v4.5.4

Compare Source

Bug Fixes

• scope the source of the secrets_manager_to_cos auth policy to the resource group (#​516) (5e481cc)

v4.5.3

Compare Source

Bug Fixes

• deps: update DAs IBM provider version to 1.56.1 (#​543)

v4.5.2

Compare Source

⚠️ This release will currently not deploy in IBM Schematics due to a known provider bug. Please use v4.5.3 which has the fix for this if running in IBM Schematics.

Bug Fixes

• update to landing-zone-vsi v2.5.0 (#​535) (c91b619)

⚠️ Warning

If you are upgrading from a previous release, and you are using the override JSON to provision additional VSI data volumes using the block_storage_volumes value, the terraform plan will tell you that it wants to destroy the volumes that are in the Default resource group and recreate them in the same resource group that the VSIs are provisioned in.

If indeed you wish to continue to keep your data volumes in the Default resource group (to prevent them from being destroyed and recreated on upgrade), you can achieve this by adding the Default resource group ID into the block_storage_volumes array in the vsi part of the override JSON. For example:

{
.....
  "vsi": [
    {
        "boot_volume_encryption_key_name": "PREFIX-vsi-volume-key",
        "image_name": "ibm-redhat-8-6-minimal-amd64-5",
        "machine_type": "cx2-8x16",
        "name": "sbx-workload",
        "resource_group": "PREFIX-workload-rg",
        "block_storage_volumes": [
            {
                "name":           "datavol",
                "profile":        "general-purpose",
                "capacity":       100,
                "encryption_key": "PREFIX-vsi-volume-key",
                "resource_group_id" : "65xxxxxxxxxxxxxxxa3fd"
            }
        ]
....
    }
  ]
....
}

v4.5.1

Compare Source

⚠️ This release will currently not deploy in IBM Schematics due to a known provider bug. Please use v4.5.3 which has the fix for this if running in IBM Schematics.

Bug Fixes

• Migrate DAs to FSCloud profile version 1.4.0 (#​524) (d89833d)

v4.5.0

Compare Source

⚠️ This release will currently not deploy in IBM Schematics due to a known provider bug. Please use v4.5.3 which has the fix for this if running in IBM Schematics.

Features

• added functionality to attach access tags to resources in. (#​447) (f4c3e3a)
  The resources which support access tags are:
  - Cluster
  - COS
  - VPE
  - VPN
  - KMS
  - Secrets Manager
  - Security Groups
  - VSIs (Bastion, F5, standard VSI)
  
  In order to utilize the access tags for a resource you will need to add a field to the override.json. For example, below is a snippet on how to add access tags to KMS:

{
  "key_management": {
    "access_tags": ["tag-group:tag-name"]
  }
}

NOTE: creating access tags via Terraform is currently not supported. This module only enables tagging resources with already existing access tags. For more information on creating these access tags, see https://cloud.ibm.com/docs/account?topic=account-access-tags-tutorial.

v4.4.7

Compare Source

Bug Fixes

• lock OCP DA version into OCP 4.12 and add validation (#​511) (ae8f462)

---

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 becomes conflicted, 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-dev]

/run pipeline

[terraform-ibm-modules-dev]

/run pipeline

[terraform-ibm-modules-ops]

Edited/Blocked Notification

Renovate will not automatically rebase this PR, because it does not recognize the last commit author and assumes somebody else may have edited the PR.

You can manually request rebase by checking the rebase/retry box above.

⚠ Warning: custom changes will be lost.

[terraform-ibm-modules-dev]

/run pipeline

[terraform-ibm-modules-dev]

/run pipeline

[terraform-ibm-modules-dev]

/run pipeline

[terraform-ibm-modules-dev]

/run pipeline

[terraform-ibm-modules-dev]

/run pipeline

[terraform-ibm-modules-dev]

/run pipeline

[terraform-ibm-modules-dev]

/run pipeline

[terraform-ibm-modules-dev]

/run pipeline