Enhancement | base-network: Update versions constraint #555
Conversation
Infracost report💰 Monthly cost will not changeCost details |
terraform commandsleverage terraform init[12:48:48.830] INFO Checking environment name definition in account.tfvars... [12:48:48.837] INFO Checking backend key... [12:48:48.842] INFO Checking backend.tfvars: [12:48:48.845] INFO Checking if profile starts with bb-apps-devstg... [12:48:48.848] INFO Checking if bucket starts with bb-apps-devstg... [12:48:48.851] INFO Checking if dynamodb table starts with bb-apps-devstg... [15:48:54] INFO Attempting to get temporary credentials for apps-devstg account. Initializing the backend... Initializing provider plugins...
Terraform has been successfully initialized! You may now begin working with Terraform. Try running "terraform plan" to see If you ever set or change modules or backend configuration for Terraform, leverage terraform plan[15:49:26] INFO Attempting to get temporary credentials for apps-devstg account. Note: Objects have changed outside of Terraform Terraform detected the following changes made outside of Terraform since the last "terraform apply" which may module.vpc_endpoints["s3"].aws_vpc_endpoint.this["endpoint"] has changed~ resource "aws_vpc_endpoint" "this" { module.vpc_peering_apps_devstg_to_eks_clusters["apps-devstg-k8s-eks"].aws_route.peer_routes[0] has been deleted
module.vpc_peering_apps_devstg_to_eks_clusters["apps-devstg-k8s-eks"].aws_route.peer_routes[1] has been deleted
module.vpc_peering_apps_devstg_to_eks_clusters["apps-devstg-k8s-eks-demoapps"].aws_route.peer_routes[0] has been deleted
module.vpc_peering_apps_devstg_to_eks_clusters["apps-devstg-k8s-eks-demoapps"].aws_route.peer_routes[1] has been deleted
Unless you have made equivalent changes to your configuration, or ignored the relevant attributes using ─────────────────────────────────────────────────────────────────────────────────────────────────────────────── Terraform used the selected providers to generate the following execution plan. Resource actions are indicated
Terraform will perform the following actions: module.vpc_flow_logs.aws_s3_bucket_policy.this[0] will be created
module.vpc_peering_apps_devstg_to_eks_clusters["apps-devstg-k8s-eks"].aws_route.peer_routes[0] will be created
module.vpc_peering_apps_devstg_to_eks_clusters["apps-devstg-k8s-eks"].aws_route.peer_routes[1] will be created
module.vpc_peering_apps_devstg_to_eks_clusters["apps-devstg-k8s-eks-demoapps"].aws_route.peer_routes[0] will be created
module.vpc_peering_apps_devstg_to_eks_clusters["apps-devstg-k8s-eks-demoapps"].aws_route.peer_routes[1] will be created
Plan: 5 to add, 0 to change, 0 to destroy. ─────────────────────────────────────────────────────────────────────────────────────────────────────────────── Note: You didn't use the -out option to save this plan, so Terraform can't guarantee to take exactly these |
crcedenop
changed the title
|
I updated with the suggested version 1.3 and the output was that leverage terraform commandsleverage terraform init[15:29:33.708] INFO Checking environment name definition in account.tfvars... [15:29:33.714] INFO Checking backend key... [15:29:33.719] INFO Checking backend.tfvars: [15:29:33.720] INFO Checking if profile starts with bb-apps-devstg... [15:29:33.725] INFO Checking if bucket starts with bb-apps-devstg... [15:29:33.729] INFO Checking if dynamodb table starts with bb-apps-devstg... [18:29:39] INFO Attempting to get temporary credentials for apps-devstg account. Initializing the backend... Initializing provider plugins...
Terraform has been successfully initialized! You may now begin working with Terraform. Try running "terraform plan" to see If you ever set or change modules or backend configuration for Terraform, leverage terraform plan[18:30:29] INFO Attempting to get temporary credentials for apps-devstg account. Note: Objects have changed outside of Terraform Terraform detected the following changes made outside of Terraform since the last "terraform apply" which may module.vpc_endpoints["s3"].aws_vpc_endpoint.this["endpoint"] has changed~ resource "aws_vpc_endpoint" "this" { module.vpc_peering_apps_devstg_to_eks_clusters["apps-devstg-k8s-eks"].aws_route.peer_routes[0] has been deleted
module.vpc_peering_apps_devstg_to_eks_clusters["apps-devstg-k8s-eks"].aws_route.peer_routes[1] has been deleted
module.vpc_peering_apps_devstg_to_eks_clusters["apps-devstg-k8s-eks-demoapps"].aws_route.peer_routes[0] has been deleted
module.vpc_peering_apps_devstg_to_eks_clusters["apps-devstg-k8s-eks-demoapps"].aws_route.peer_routes[1] has been deleted
Unless you have made equivalent changes to your configuration, or ignored the relevant attributes using ─────────────────────────────────────────────────────────────────────────────────────────────────────────────── Terraform used the selected providers to generate the following execution plan. Resource actions are indicated
Terraform will perform the following actions: module.vpc_flow_logs.aws_s3_bucket_policy.this[0] will be created
module.vpc_peering_apps_devstg_to_eks_clusters["apps-devstg-k8s-eks"].aws_route.peer_routes[0] will be created
module.vpc_peering_apps_devstg_to_eks_clusters["apps-devstg-k8s-eks"].aws_route.peer_routes[1] will be created
module.vpc_peering_apps_devstg_to_eks_clusters["apps-devstg-k8s-eks-demoapps"].aws_route.peer_routes[0] will be created
module.vpc_peering_apps_devstg_to_eks_clusters["apps-devstg-k8s-eks-demoapps"].aws_route.peer_routes[1] will be created
Plan: 5 to add, 0 to change, 0 to destroy. ─────────────────────────────────────────────────────────────────────────────────────────────────────────────── Note: You didn't use the -out option to save this plan, so Terraform can't guarantee to take exactly these |
exequielrafaela
deleted the
feature/apps-devstg-base-network-update-tf-versions
branch
What?
How?
Environment Versions
Layers
Why?
References