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

Deploy VPC in us-east-1 #149

Merged
merged 2 commits into from
Apr 23, 2024
Merged

Deploy VPC in us-east-1 #149

merged 2 commits into from
Apr 23, 2024

Conversation

soerenmartius
Copy link
Contributor

@soerenmartius soerenmartius commented Apr 23, 2024

This PR deploys a new VPC in the us-east-1 region.

@soerenmartius soerenmartius requested a review from a team as a code owner April 23, 2024 12:17
Copy link

github-actions bot commented Apr 23, 2024

Preview of Terraform changes in f91e0d3

🔍 View Details on Terramate Cloud

Changed Stacks

prod/us-east-1/vpc

Terraform Plan

terramate: Entering stack in /stacks/prod/us-east-1/vpc
terramate: Executing command "terraform show -no-color out.tfplan"

Terraform used the selected providers to generate the following execution
plan. Resource actions are indicated with the following symbols:
  ~ update in-place

Terraform will perform the following actions:

  # module.vpc.aws_subnet.private[0] will be updated in-place
  ~ resource "aws_subnet" "private" {
        id                                             = "subnet-0b687a1a99e5dc199"
      ~ tags                                           = {
            "Environment" = "prd"
          + "Foo"         = "bar"
            "Name"        = "prd-vpc-private-us-east-1a"
            "Terraform"   = "true"
            "Tier"        = "private"
        }
      ~ tags_all                                       = {
          + "Foo"         = "bar"
            # (4 unchanged elements hidden)
        }
        # (15 unchanged attributes hidden)
    }

  # module.vpc.aws_subnet.private[1] will be updated in-place
  ~ resource "aws_subnet" "private" {
        id                                             = "subnet-020f7a564e63b7e52"
      ~ tags                                           = {
            "Environment" = "prd"
          + "Foo"         = "bar"
            "Name"        = "prd-vpc-private-us-east-1b"
            "Terraform"   = "true"
            "Tier"        = "private"
        }
      ~ tags_all                                       = {
          + "Foo"         = "bar"
            # (4 unchanged elements hidden)
        }
        # (15 unchanged attributes hidden)
    }

  # module.vpc.aws_subnet.private[2] will be updated in-place
  ~ resource "aws_subnet" "private" {
        id                                             = "subnet-00ac668e5d9b48944"
      ~ tags                                           = {
            "Environment" = "prd"
          + "Foo"         = "bar"
            "Name"        = "prd-vpc-private-us-east-1c"
            "Terraform"   = "true"
            "Tier"        = "private"
        }
      ~ tags_all                                       = {
          + "Foo"         = "bar"
            # (4 unchanged elements hidden)
        }
        # (15 unchanged attributes hidden)
    }

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

@soerenmartius soerenmartius force-pushed the soerenmartius/trigger-vpc branch from ac7b904 to f91e0d3 Compare April 23, 2024 12:21
@soerenmartius soerenmartius merged commit 090d849 into main Apr 23, 2024
1 check passed
@soerenmartius soerenmartius deleted the soerenmartius/trigger-vpc branch April 23, 2024 12:23
@soerenmartius soerenmartius changed the title Trigger VPC Deploy VPC in us-east-1 May 7, 2024
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.

1 participant