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

feat: Add support for transit gateway CIDR blocks #69

Merged

Conversation

bryantbiggs
Copy link
Member

Description

  • Add support for transit gateway CIDR blocks
  • Change var.amazon_side_asn default to null which defaults to "64512"
  • Add configurable timeouts block to transit gateway

Motivation and Context

Breaking Changes

  • No

How Has This Been Tested?

  • I have tested and validated these changes using one or more of the provided examples/* projects
    • Tested on examples/complete

transit_gateway_cidr_blocks = var.transit_gateway_cidr_blocks

timeouts {
create = try(var.timeouts.create, null)
Copy link
Member

Choose a reason for hiding this comment

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

Just wondering if we should write vars like this or var.timeouts["create"]? What is more correct? I think we write it like var.timeouts["create"] in most places. Are there any drawbacks/benefits of any? I am lost :)

Copy link
Member Author

Choose a reason for hiding this comment

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

I don't think there are any drawbacks of one way vs the other - this way was just less characters and fit with the other try() usage patterns

@antonbabenko antonbabenko merged commit 131ed50 into terraform-aws-modules:master Mar 26, 2022
antonbabenko pushed a commit that referenced this pull request Mar 26, 2022
## [2.7.0](v2.6.0...v2.7.0) (2022-03-26)

### Features

* Add support for transit gateway CIDR blocks ([#69](#69)) ([131ed50](131ed50))
@antonbabenko
Copy link
Member

This PR is included in version 2.7.0 🎉

@bryantbiggs bryantbiggs deleted the feat/cidr-blocks branch March 26, 2022 21:06
@tsybanov
Copy link

Thank you for the PR @bryantbiggs !

Why has the major AWS Requirement version been bumped without bumping the major version of this module? Otherwise, it brakes ~> 2.0 version of this module with the AWS ~> 3.0 version across the board.

@github-actions
Copy link

I'm going to lock this pull request because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues. If you have found a problem that seems related to this change, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.

@github-actions github-actions bot locked as resolved and limited conversation to collaborators Oct 28, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants