Skip to content
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.

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

Refactoring + introduce allow dns resolution binding #429

Merged
merged 17 commits into from
Nov 7, 2023

Conversation

vburckhardt
Copy link
Member

@vburckhardt vburckhardt commented Nov 3, 2023

Description

Related to terraform-ibm-modules/terraform-ibm-landing-zone-vpc#652

Found some inconsistencies / anti-pattern as I was adding the allow_dns_resolution_binding input in the module. This PR exposes allow_dns_resolution_binding but also fixes those inconsistencies as opposed to build on top of a fragile foundation.

  • Fix internal inconsistencies between the way the VPE details were passed for multi-tenant and single-tenant VPEs (cloud_services and cloud_service_by_crn variable now follow the same type and naming conventions)
  • Renamed some fields to more accurate and precise terms
  • Removed vpe_names variable. This is now replace with the vpe_name field in the cloud_services and cloud_service_by_crn
  • Also fixed a bug where the reserved ips were not named

Whilst the interface of module changes, there is no deletion of resources when moving up to this new version, assuming to coherent parameters are passed as input.

Release required?

  • No release
  • Patch release (x.x.X)
  • Minor release (x.X.x)
  • Major release (X.x.x)
Release notes content

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
Copy link
Member Author

/run pipeline

@vburckhardt
Copy link
Member Author

/run pipeline

@vburckhardt
Copy link
Member Author

vburckhardt commented Nov 3, 2023

  • TODO: adjust readme usage

@vburckhardt
Copy link
Member Author

/run pipeline

@vburckhardt
Copy link
Member Author

/run pipeline

2 similar comments
@vburckhardt
Copy link
Member Author

/run pipeline

@vburckhardt
Copy link
Member Author

/run pipeline

…-vpe-gateway into allow-dns-resolution-binding
toddgiguere
toddgiguere previously approved these changes Nov 7, 2023
@vburckhardt vburckhardt dismissed toddgiguere’s stale review November 7, 2023 14:50

The merge-base changed after approval.

@vburckhardt
Copy link
Member Author

/run pipeline

@vburckhardt vburckhardt merged commit a6b7a5f into main Nov 7, 2023
2 checks passed
@vburckhardt vburckhardt deleted the allow-dns-resolution-binding branch November 7, 2023 16:38
@terraform-ibm-modules-ops
Copy link
Contributor

🎉 This PR is included in version 4.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
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants