Skip to content

Conversation

@imprateeksh
Copy link
Member

@imprateeksh imprateeksh commented Aug 18, 2025

Description

This PR is to include the documentation about the deprecation of in-module VPN gateway provisioning in the Landing Zone VPC module mentioning about planned removal in upcoming release. The intention is to remove the direct usage of resource in root module and consume site to site VPN module.

Release required?

  • No release
  • Patch release (x.x.X)
  • Minor release (x.X.x)
  • Major release (X.x.x)
Release notes content
  • Resource address changes:
    Root‑level ibm_is_vpn_gateway resource will be refactored into the vpn_gateways module. Once this is done, users must migrate state using terraform state mv command to avoid recreation of ibm_is_vpn_gateway resource.

    Example:

      terraform state mv \
        'module.slz_vpc.ibm_is_vpn_gateway.vpn_gateway["vpg1"]' \
        'module.slz_vpc.module.vpn_gateways["vpg1"].ibm_is_vpn_gateway.vpn_gateway[0]'

Run the pipeline

If the CI pipeline doesn't run when you create the PR, the PR requires a user with GitHub collaborators access to run the pipeline.

Run the CI pipeline when the PR is ready for review and you expect tests to pass. Add a comment to the PR with the following text:

/run pipeline

Checklist for reviewers

  • If relevant, a test for the change is included or updated with this PR.
  • If relevant, documentation for the change is included or updated with this PR.

For mergers

  • Use a conventional commit message to set the release level. Follow the guidelines.
  • Include information that users need to know about the PR in the commit message. The commit message becomes part of the GitHub release notes.
  • Use the Squash and merge option.

vburckhardt
vburckhardt previously approved these changes Sep 3, 2025
@imprateeksh
Copy link
Member Author

/run pipeline

@imprateeksh imprateeksh requested a review from ocofaigh December 4, 2025 12:36
@imprateeksh
Copy link
Member Author

Marked this as major release as per the comment given in the internal issue i.e. getting the new major version released with a migration guide.

@imprateeksh
Copy link
Member Author

Before migrating state - Recreation of resource can be seen

image image image

After Migration : Resource recreation is not happening
image

image

Copy link
Contributor

@ocofaigh ocofaigh left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

left some comments


## ⚠️ Deprecation Notice

In the upcoming version, the direct use of `ibm_is_vpn_gateway` resources in the root module will be **deprecated**.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

what upcoming versions? Lets not get mixed up between "deprecated" and "removed". Deprecated simply means there is an alternative way to deploy, and eventually the feature will be removed. So technically the feature is already deprecated.

also this doc should not be referencing the provider resource, but instead the actual featiure that is being depreciated (aka VPN gateway)

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@ocofaigh - By upcoming version I meant to make use of the next release as some code changes are required. I will connect with you about this point as I have some doubt here.

module.subnets.ibm_is_vpc_address_prefix.subnet_prefix["gcat-multizone-subnet-c"]
```

## ​ Upgrade Guide: Migrating VPN from Landing Zone VPC Module to Standalone Site-to-Site VPN Module
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The root readme should not contain all this information. There should be a one liner deprecation warning at the top of the readme that point to .docs/migration_guide.md (Also why did you make it a hidden folder (.doc) ?

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Got it and my bad w.r.t hidden folder, I thought we are making use of this docs directory for documentation. I will move it out at the root level. Thank you.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

In the one-liner notice add some ⚠️ warning symbols, and point it to the readme file in the docs folder.

##############################################################################

variable "vpn_gateways" {
description = "List of VPN gateways to create."
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I would add [DEPRECATED] to this description and link to the deprecation doc.

module.subnets.ibm_is_vpc_address_prefix.subnet_prefix["gcat-multizone-subnet-c"]
```

## ​ Upgrade Guide: Migrating VPN from Landing Zone VPC Module to Standalone Site-to-Site VPN Module
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

In the one-liner notice add some ⚠️ warning symbols, and point it to the readme file in the docs folder.

##############################################################################
# Create VPN Gateways
##############################################################################
# ⚠️ Provisioning of VPN Gateways will soon be deprecated.
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Maybe add URL for the migration_guide.md here too.

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

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants