Skip to content

chore(deps): update terraform-module #813

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom
Merged
merged 3 commits into from
Apr 3, 2025
Merged

chore(deps): update terraform-module #813

merged 3 commits into from
Apr 3, 2025

Conversation

terraform-ibm-modules-ops
Copy link
Contributor

@terraform-ibm-modules-ops terraform-ibm-modules-ops commented Mar 29, 2025 •
edited
Loading

This PR contains the following updates:

Package Type Update Change
terraform-ibm-modules/kms-all-inclusive/ibm (source) module patch 4.21.3 -> 4.21.4
terraform-ibm-modules/landing-zone-vpc/ibm (source) module minor 7.20.2 -> 7.22.2

Release Notes

terraform-ibm-modules/terraform-ibm-kms-all-inclusive (terraform-ibm-modules/kms-all-inclusive/ibm)

v4.21.4

Compare Source

Bug Fixes
  • deps: update terraform ibm to latest for the deployable architecture solution (#​639) (55659a2)
terraform-ibm-modules/terraform-ibm-landing-zone-vpc (terraform-ibm-modules/landing-zone-vpc/ibm)

v7.22.2

Compare Source

Bug Fixes
  • deps: update terraform ibm to latest for deployable architectures (#​943) (4e5a00f)

v7.22.1

Compare Source

Bug Fixes

v7.22.0

Compare Source

Features
  • Scope auth policy for flow logs to exact cos bucket

    NOTE: When upgrading from a previous version, you will see a recreate of this auth policy, however new auth policy will be created before destroyed so there will be no disruption to everyday services (#​941) (032c772)

v7.21.0

Compare Source

Features

(#​915) (33309f8)

  • added support to the module create VPC gateways using new input vpn_gateways
  • added support to the module for subnet specific tagging by adding a new subnet_tags attribute to the subnets input.
  • Added new DA for IBM Cloud catalog

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
Copy link
Contributor

/run pipeline

@terraform-ibm-modules-ops terraform-ibm-modules-ops changed the title chore(deps): update terraform terraform-ibm-modules/landing-zone-vpc/ibm to v7.22.0 chore(deps): update terraform terraform-ibm-modules/landing-zone-vpc/ibm to v7.22.1 Mar 30, 2025
@terraform-ibm-modules-dev
Copy link
Contributor

/run pipeline

@terraform-ibm-modules-ops terraform-ibm-modules-ops changed the title chore(deps): update terraform terraform-ibm-modules/landing-zone-vpc/ibm to v7.22.1 chore(deps): update terraform terraform-ibm-modules/landing-zone-vpc/ibm to v7.22.2 Mar 30, 2025
@terraform-ibm-modules-dev
Copy link
Contributor

/run pipeline

@terraform-ibm-modules-ops terraform-ibm-modules-ops changed the title chore(deps): update terraform terraform-ibm-modules/landing-zone-vpc/ibm to v7.22.2 chore(deps): update terraform-module Mar 30, 2025
@terraform-ibm-modules-dev
Copy link
Contributor

/run pipeline

@Aashiq-J
Copy link
Member

Aashiq-J commented Apr 2, 2025

/run pipeline

@Aashiq-J
Copy link
Member

Aashiq-J commented Apr 3, 2025 

 # module.slz_vpc.ibm_is_vpc.vpc[0] will be updated in-place
  ~ resource "ibm_is_vpc" "vpc" {
        id                          = "r006-30de7b2b-34c9-47af-bad7-6ca68d6948e3"
      ~ name                        = "vni-apr3-vpc-vpc" -> "vni-apr3-vpc"
        tags                        = []
        # (27 unchanged attributes hidden)

        # (1 unchanged block hidden)
    }

  # module.slz_vsi.data.ibm_is_vpc.vpc will be read during apply
  # (depends on a resource or a module with changes pending)
 <= data "ibm_is_vpc" "vpc" {
      + access_tags                 = (known after apply)
      + classic_access              = (known after apply)
      + crn                         = (known after apply)
      + cse_source_addresses        = (known after apply)
      + default_address_prefixes    = (known after apply)
      + default_network_acl         = (known after apply)
      + default_network_acl_crn     = (known after apply)
      + default_network_acl_name    = (known after apply)
      + default_routing_table       = (known after apply)
      + default_routing_table_name  = (known after apply)
      + default_security_group      = (known after apply)
      + default_security_group_crn  = (known after apply)
      + default_security_group_name = (known after apply)
      + dns                         = (known after apply)
      + health_reasons              = (known after apply)
      + health_state                = (known after apply)
      + id                          = (known after apply)
      + identifier                  = "r006-30de7b2b-34c9-47af-bad7-6ca68d6948e3"
      + resource_controller_url     = (known after apply)
      + resource_crn                = (known after apply)
      + resource_group              = (known after apply)
      + resource_group_name         = (known after apply)
      + resource_name               = (known after apply)
      + resource_status             = (known after apply)
      + security_group              = (known after apply)
      + status                      = (known after apply)
      + subnets                     = (known after apply)
      + tags                        = (known after apply)
    }

  # module.slz_vsi.ibm_is_virtual_network_interface.primary_vni["vni-apr3-vpc-subnet-a-0"] will be updated in-place
  ~ resource "ibm_is_virtual_network_interface" "primary_vni" {
        id                            = "0717-ac47c37d-51e5-497a-9bee-1494e9db9189"
        name                          = "vni-apr3-vpc-subnet-a-vsi-name-1-vni"
      ~ security_groups               = [
          - "r006-032db86f-fae4-4648-80a3-62878a9839c6",
        ] -> (known after apply)
        tags                          = []
        # (16 unchanged attributes hidden)

        # (3 unchanged blocks hidden)
    }

  # module.slz_vsi.ibm_is_virtual_network_interface.primary_vni["vni-apr3-vpc-subnet-b-0"] will be updated in-place
  ~ resource "ibm_is_virtual_network_interface" "primary_vni" {
        id                            = "0727-c25eab13-9e76-42f6-b3a6-0fec12cb6705"
        name                          = "vni-apr3-vpc-subnet-b-vsi-name-1-vni"
      ~ security_groups               = [
          - "r006-032db86f-fae4-4648-80a3-62878a9839c6",
        ] -> (known after apply)
        tags                          = []
        # (16 unchanged attributes hidden)

        # (3 unchanged blocks hidden)
    }

  # module.slz_vsi.ibm_is_virtual_network_interface.primary_vni["vni-apr3-vpc-subnet-c-0"] will be updated in-place
  ~ resource "ibm_is_virtual_network_interface" "primary_vni" {
        id                            = "0737-4a0aa055-abfe-4588-80ba-2207b45c23a1"
        name                          = "vni-apr3-vpc-subnet-c-vsi-name-1-vni"
      ~ security_groups               = [
          - "r006-032db86f-fae4-4648-80a3-62878a9839c6",
        ] -> (known after apply)
        tags                          = []
        # (16 unchanged attributes hidden)

        # (3 unchanged blocks hidden)
    }

  # module.slz_vsi.ibm_is_virtual_network_interface.secondary_vni["vni-apr3-second-subnet-a-0"] will be updated in-place
  ~ resource "ibm_is_virtual_network_interface" "secondary_vni" {
        id                            = "0717-9c12aead-30d2-409c-a8cb-5386397535cb"
        name                          = "vni-apr3-second-subnet-a-0"
      ~ security_groups               = [
          - "r006-032db86f-fae4-4648-80a3-62878a9839c6",
        ] -> (known after apply)
        tags                          = []
        # (16 unchanged attributes hidden)

        # (1 unchanged block hidden)
    }

  # module.slz_vsi.ibm_is_virtual_network_interface.secondary_vni["vni-apr3-second-subnet-b-0"] will be updated in-place
  ~ resource "ibm_is_virtual_network_interface" "secondary_vni" {
        id                            = "0727-6cd21988-1c8b-4092-8027-a66c78a7bf0a"
        name                          = "vni-apr3-second-subnet-b-0"
      ~ security_groups               = [
          - "r006-032db86f-fae4-4648-80a3-62878a9839c6",
        ] -> (known after apply)
        tags                          = []
        # (16 unchanged attributes hidden)

        # (1 unchanged block hidden)
    }

  # module.slz_vsi.ibm_is_virtual_network_interface.secondary_vni["vni-apr3-second-subnet-c-0"] will be updated in-place
  ~ resource "ibm_is_virtual_network_interface" "secondary_vni" {
        id                            = "0737-a0d7d269-d2db-4dcf-8837-a8c845f42fef"
        name                          = "vni-apr3-second-subnet-c-0"
      ~ security_groups               = [
          - "r006-032db86f-fae4-4648-80a3-62878a9839c6",
        ] -> (known after apply)
        tags                          = []
        # (16 unchanged attributes hidden)

        # (1 unchanged block hidden)
    }

Plan: 0 to add, 7 to change, 0 to destroy.

Changes to Outputs:
  ~ slz_vpc                   = {
      + security_group_details       = {}
      ~ vpc_data                     = {
            id                          = "r006-30de7b2b-34c9-47af-bad7-6ca68d6948e3"
            name                        = "vni-apr3-vpc-vpc"
          ~ subnets                     = [
              ~ {
                  ~ available_ipv4_address_count = 251 -> 248
                    id                           = "0727-7eb9f299-6c18-4cd8-8377-f877b49bff90"
                    name                         = "vni-apr3-vpc-subnet-b"
                    # (3 unchanged attributes hidden)
                },
              ~ {
                  ~ available_ipv4_address_count = 251 -> 247
                    id                           = "0737-01eb071e-1e2c-4106-850b-87a873f8df9d"
                    name                         = "vni-apr3-vpc-subnet-c"
                    # (3 unchanged attributes hidden)
                },
              ~ {
                  ~ available_ipv4_address_count = 251 -> 245
                    id                           = "0717-3ef9aac4-49ee-458e-9da8-294615cb260c"
                    name                         = "vni-apr3-vpc-subnet-a"
                    # (3 unchanged attributes hidden)
                },
              ~ {
                  ~ available_ipv4_address_count = 251 -> 250
                    id                           = "0717-83435602-4f67-44a5-954f-d1c4c1a6e1fb"
                    name                         = "vni-apr3-second-subnet-a"
                    # (3 unchanged attributes hidden)
                },
              ~ {
                  ~ available_ipv4_address_count = 251 -> 250
                    id                           = "0727-09cae020-91e0-4aa9-b800-3bdbe6baf1e9"
                    name                         = "vni-apr3-second-subnet-b"
                    # (3 unchanged attributes hidden)
                },
              ~ {
                  ~ available_ipv4_address_count = 251 -> 250
                    id                           = "0737-4ae10193-0e1f-4c5c-8176-352ab89bbd0d"
                    name                         = "vni-apr3-second-subnet-c"
                    # (3 unchanged attributes hidden)
                },
            ]
            tags                        = []
            # (25 unchanged attributes hidden)
        }
      ~ vpc_name                     = "vni-apr3-vpc-vpc" -> "vni-apr3-vpc"
      + vpn_gateways_data            = []
      + vpn_gateways_name            = []
        # (19 unchanged attributes hidden)
    }

Changes are just update-in-place, no breaking change. The only change here is the renaming of the vpc.
skipping the upgrade test

@Aashiq-J
Copy link
Member

Aashiq-J commented Apr 3, 2025

/run pipeline

@Aashiq-J Aashiq-J merged commit a881a7c into main Apr 3, 2025
2 checks passed
@Aashiq-J Aashiq-J deleted the renovate/terraform-module branch April 3, 2025 06:38
@terraform-ibm-modules-ops
Copy link
Contributor Author

🎉 This PR is included in version 5.0.0 🎉

The release is available on GitHub release

Your semantic-release bot 📦🚀

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers

@Aashiq-J Aashiq-J Aashiq-J approved these changes

@toddgiguere toddgiguere Awaiting requested review from toddgiguere toddgiguere is a code owner

Assignees
No one assigned
Labels
released renovate
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
3 participants
@terraform-ibm-modules-ops @terraform-ibm-modules-dev @Aashiq-J