Skip to content

Conversation

axxander
Copy link
Owner

No description provided.

@axxander
Copy link
Owner Author

atlantis plan

@axxander axxander closed this Apr 10, 2023
@axxander axxander reopened this Apr 10, 2023
@axxander axxander closed this Apr 10, 2023
@axxander axxander reopened this Apr 10, 2023
@axxander
Copy link
Owner Author

atlantis plan

@axxander
Copy link
Owner Author

Plan Error

parsing atlantis.yaml: repo config not allowed to set 'workflow' key: server-side config needs 'allowed_overrides: [workflow]'

@axxander
Copy link
Owner Author

Plan Error

parsing atlantis.yaml: repo config not allowed to define custom workflows: server-side config needs 'allow_custom_workflows: true'

@axxander
Copy link
Owner Author

atlantis plan

@axxander
Copy link
Owner Author

Plan Error

parsing atlantis.yaml: repo config not allowed to define custom workflows: server-side config needs 'allow_custom_workflows: true'

@axxander
Copy link
Owner Author

atlantis plan

@axxander
Copy link
Owner Author

Ran Plan for dir: terraform/aws/alexgregorydotio-prod workspace: default

Plan Error

running "/opt/homebrew/bin/terraform plan -input=false -refresh -out \"/Users/alexgregory/.atlantis/repos/axxander/platform/3/default/terraform/aws/alexgregorydotio-prod/prod-default.tfplan\"" in "/Users/alexgregory/.atlantis/repos/axxander/platform/3/default/terraform/aws/alexgregorydotio-prod": exit status 1
╷
│ Error: No configuration files
│ 
│ Plan requires configuration to be present. Planning without a configuration
│ would mark everything for destruction, which is normally not what is
│ desired. If you would like to destroy everything, run plan with the
│ -destroy option. Otherwise, create a Terraform configuration file (.tf
│ file) and try again.
╵

@axxander
Copy link
Owner Author

atlantis plan

@axxander
Copy link
Owner Author

Ran Plan for dir: terraform/aws/alexgregorydotio-prod workspace: default

Plan Error

running "/opt/homebrew/bin/terraform plan -input=false -refresh -out \"/Users/alexgregory/.atlantis/repos/axxander/platform/3/default/terraform/aws/alexgregorydotio-prod/prod-default.tfplan\"" in "/Users/alexgregory/.atlantis/repos/axxander/platform/3/default/terraform/aws/alexgregorydotio-prod": exit status 1
╷
│ Error: No configuration files
│ 
│ Plan requires configuration to be present. Planning without a configuration
│ would mark everything for destruction, which is normally not what is
│ desired. If you would like to destroy everything, run plan with the
│ -destroy option. Otherwise, create a Terraform configuration file (.tf
│ file) and try again.
╵

@axxander
Copy link
Owner Author

atlantis plan

@axxander
Copy link
Owner Author

Plan Error

parsing atlantis.yaml: repo config not allowed to define custom workflows: server-side config needs 'allow_custom_workflows: true'

@axxander
Copy link
Owner Author

atlantis plan

@axxander
Copy link
Owner Author

Plan Error

parsing atlantis.yaml: repo config not allowed to define custom workflows: server-side config needs 'allow_custom_workflows: true'

@axxander
Copy link
Owner Author

atlantis plan

1 similar comment
@axxander
Copy link
Owner Author

atlantis plan

@axxander
Copy link
Owner Author

Ran Plan for dir: terraform/aws/alexgregorydotio-prod workspace: default

Plan Error

running "/opt/homebrew/bin/terraform plan -input=false -refresh -out \"/Users/alexgregory/.atlantis/repos/axxander/platform/3/default/terraform/aws/alexgregorydotio-prod/prod-default.tfplan\"" in "/Users/alexgregory/.atlantis/repos/axxander/platform/3/default/terraform/aws/alexgregorydotio-prod": exit status 1
╷
│ Error: No configuration files
│ 
│ Plan requires configuration to be present. Planning without a configuration
│ would mark everything for destruction, which is normally not what is
│ desired. If you would like to destroy everything, run plan with the
│ -destroy option. Otherwise, create a Terraform configuration file (.tf
│ file) and try again.
╵

1 similar comment
@axxander
Copy link
Owner Author

Ran Plan for dir: terraform/aws/alexgregorydotio-prod workspace: default

Plan Error

running "/opt/homebrew/bin/terraform plan -input=false -refresh -out \"/Users/alexgregory/.atlantis/repos/axxander/platform/3/default/terraform/aws/alexgregorydotio-prod/prod-default.tfplan\"" in "/Users/alexgregory/.atlantis/repos/axxander/platform/3/default/terraform/aws/alexgregorydotio-prod": exit status 1
╷
│ Error: No configuration files
│ 
│ Plan requires configuration to be present. Planning without a configuration
│ would mark everything for destruction, which is normally not what is
│ desired. If you would like to destroy everything, run plan with the
│ -destroy option. Otherwise, create a Terraform configuration file (.tf
│ file) and try again.
╵

@axxander
Copy link
Owner Author

atlantis plan

@axxander
Copy link
Owner Author

Ran Plan for dir: terraform/aws/alexgregorydotio-prod workspace: default

Plan Error

running "/opt/homebrew/bin/terraform plan -input=false -refresh -out \"/Users/alexgregory/.atlantis/repos/axxander/platform/3/default/terraform/aws/alexgregorydotio-prod/prod-default.tfplan\"" in "/Users/alexgregory/.atlantis/repos/axxander/platform/3/default/terraform/aws/alexgregorydotio-prod": exit status 1
╷
│ Error: No configuration files
│ 
│ Plan requires configuration to be present. Planning without a configuration
│ would mark everything for destruction, which is normally not what is
│ desired. If you would like to destroy everything, run plan with the
│ -destroy option. Otherwise, create a Terraform configuration file (.tf
│ file) and try again.
╵

@axxander
Copy link
Owner Author

atlantis plan

@axxander
Copy link
Owner Author

Ran Plan for dir: terraform/aws/alexgregorydotio-prod workspace: default

Plan Error

Show Output
running "terragrunt run-all plan -input=false" in "/Users/alexgregory/.atlantis/repos/axxander/platform/3/default/terraform/aws/alexgregorydotio-prod": exit status 1: running "terragrunt run-all plan -input=false" in "/Users/alexgregory/.atlantis/repos/axxander/platform/3/default/terraform/aws/alexgregorydotio-prod": 
time=2023-04-11T10:32:22+01:00 level=info msg=The stack at /Users/alexgregory/.atlantis/repos/axxander/platform/3/default/terraform/aws/alexgregorydotio-prod will be processed in the following order for command plan:
Group 1
- Module /Users/alexgregory/.atlantis/repos/axxander/platform/3/default/terraform/aws/alexgregorydotio-prod/eu-west-1/prod/example



Initializing the backend...

Successfully configured the backend "s3"! Terraform will automatically
use this backend unless the backend configuration changes.

Initializing provider plugins...
- Reusing previous version of hashicorp/aws from the dependency lock file
- Installing hashicorp/aws v4.62.0...
- Installed hashicorp/aws v4.62.0 (signed by HashiCorp)

Terraform has been successfully initialized!

You may now begin working with Terraform. Try running "terraform plan" to see
any changes that are required for your infrastructure. All Terraform commands
should now work.

If you ever set or change modules or backend configuration for Terraform,
rerun this command to reinitialize your working directory. If you forget, other
commands will detect it and remind you to do so if necessary.

Planning failed. Terraform encountered an error while generating this plan.

╷
│ Error: configuring Terraform AWS Provider: IAM Role (arn:aws:iam::912142350009:role/TerragruntRole) cannot be assumed.
│ 
│ There are a number of possible causes of this - the most common are:
│   * The credentials used in order to assume the role are invalid
│   * The credentials do not have appropriate permission to assume the role
│   * The role ARN is not valid
│ 
│ AWS Error: operation error STS: AssumeRole, https response error StatusCode: 403, RequestID: e2244f39-9bca-45ae-8a02-7f8f5a5cca44, api error AccessDenied: User: arn:aws:iam::912142350009:user/terraform is not authorized to perform: sts:AssumeRole on resource: arn:aws:iam::912142350009:role/TerragruntRole
│ 
│ 
│   with provider["registry.terraform.io/hashicorp/aws"],
│   on provider.tf line 2, in provider "aws":
│    2: provider "aws" {
│ 
╵
time=2023-04-11T10:32:43+01:00 level=error msg=Terraform invocation failed in /Users/alexgregory/.atlantis/repos/axxander/platform/3/default/terraform/aws/alexgregorydotio-prod/eu-west-1/prod/example/.terragrunt-cache/Y_shpyDtlnIaQFTYb9wiSoe22P8/06wdrOJD7Yl3z7ezhyFMJt6Gd1M/modules/aws/s3-bucket prefix=[/Users/alexgregory/.atlantis/repos/axxander/platform/3/default/terraform/aws/alexgregorydotio-prod/eu-west-1/prod/example] 
time=2023-04-11T10:32:43+01:00 level=error msg=Module /Users/alexgregory/.atlantis/repos/axxander/platform/3/default/terraform/aws/alexgregorydotio-prod/eu-west-1/prod/example has finished with an error: 1 error occurred:
	* exit status 1

 prefix=[/Users/alexgregory/.atlantis/repos/axxander/platform/3/default/terraform/aws/alexgregorydotio-prod/eu-west-1/prod/example] 
time=2023-04-11T10:32:43+01:00 level=info msg=
Initializing the backend...

Successfully configured the backend "s3"! Terraform will automatically
use this backend unless the backend configuration changes.

Initializing provider plugins...
- Reusing previous version of hashicorp/aws from the dependency lock file
- Installing hashicorp/aws v4.62.0...
- Installed hashicorp/aws v4.62.0 (signed by HashiCorp)

Terraform has been successfully initialized!

You may now begin working with Terraform. Try running "terraform plan" to see
any changes that are required for your infrastructure. All Terraform commands
should now work.

If you ever set or change modules or backend configuration for Terraform,
rerun this command to reinitialize your working directory. If you forget, other
commands will detect it and remind you to do so if necessary.
╷
│ Error: configuring Terraform AWS Provider: IAM Role (arn:aws:iam::912142350009:role/TerragruntRole) cannot be assumed.
│ 
│ There are a number of possible causes of this - the most common are:
│   * The credentials used in order to assume the role are invalid
│   * The credentials do not have appropriate permission to assume the role
│   * The role ARN is not valid
│ 
│ AWS Error: operation error STS: AssumeRole, https response error StatusCode: 403, RequestID: e2244f39-9bca-45ae-8a02-7f8f5a5cca44, api error AccessDenied: User: arn:aws:iam::912142350009:user/terraform is not authorized to perform: sts:AssumeRole on resource: arn:aws:iam::912142350009:role/TerragruntRole
│ 
│ 
│   with provider["registry.terraform.io/hashicorp/aws"],
│   on provider.tf line 2, in provider "aws":
│    2: provider "aws" {
│ 
╵
time=2023-04-11T10:32:43+01:00 level=error msg=Terraform invocation failed in /Users/alexgregory/.atlantis/repos/axxander/platform/3/default/terraform/aws/alexgregorydotio-prod/eu-west-1/prod/example/.terragrunt-cache/Y_shpyDtlnIaQFTYb9wiSoe22P8/06wdrOJD7Yl3z7ezhyFMJt6Gd1M/modules/aws/s3-bucket prefix=[/Users/alexgregory/.atlantis/repos/axxander/platform/3/default/terraform/aws/alexgregorydotio-prod/eu-west-1/prod/example] 

time=2023-04-11T10:32:43+01:00 level=error msg=1 error occurred:
	* exit status 1





@axxander
Copy link
Owner Author

atlantis plan

@axxander
Copy link
Owner Author

Ran Plan for dir: terraform/aws/alexgregorydotio-prod workspace: default

Plan Error

Show Output
running "terragrunt run-all plan -input=false" in "/Users/alexgregory/.atlantis/repos/axxander/platform/3/default/terraform/aws/alexgregorydotio-prod": exit status 1: running "terragrunt run-all plan -input=false" in "/Users/alexgregory/.atlantis/repos/axxander/platform/3/default/terraform/aws/alexgregorydotio-prod": 
time=2023-04-11T10:46:09+01:00 level=info msg=The stack at /Users/alexgregory/.atlantis/repos/axxander/platform/3/default/terraform/aws/alexgregorydotio-prod will be processed in the following order for command plan:
Group 1
- Module /Users/alexgregory/.atlantis/repos/axxander/platform/3/default/terraform/aws/alexgregorydotio-prod/eu-west-1/prod/example



Initializing the backend...

Initializing provider plugins...
- Reusing previous version of hashicorp/aws from the dependency lock file
- Using previously-installed hashicorp/aws v4.62.0

Terraform has been successfully initialized!

You may now begin working with Terraform. Try running "terraform plan" to see
any changes that are required for your infrastructure. All Terraform commands
should now work.

If you ever set or change modules or backend configuration for Terraform,
rerun this command to reinitialize your working directory. If you forget, other
commands will detect it and remind you to do so if necessary.

Planning failed. Terraform encountered an error while generating this plan.

╷
│ Error: configuring Terraform AWS Provider: IAM Role (arn:aws:iam::912142350009:role/TerragruntRole) cannot be assumed.
│ 
│ There are a number of possible causes of this - the most common are:
│   * The credentials used in order to assume the role are invalid
│   * The credentials do not have appropriate permission to assume the role
│   * The role ARN is not valid
│ 
│ AWS Error: operation error STS: AssumeRole, https response error StatusCode: 403, RequestID: 54633098-80aa-4828-bffa-5b5d14b3c7ba, api error AccessDenied: User: arn:aws:sts::912142350009:assumed-role/TerragruntRole/alex.gregory is not authorized to perform: sts:AssumeRole on resource: arn:aws:iam::912142350009:role/TerragruntRole
│ 
│ 
│   with provider["registry.terraform.io/hashicorp/aws"],
│   on provider.tf line 2, in provider "aws":
│    2: provider "aws" {
│ 
╵
time=2023-04-11T10:46:14+01:00 level=error msg=Terraform invocation failed in /Users/alexgregory/.atlantis/repos/axxander/platform/3/default/terraform/aws/alexgregorydotio-prod/eu-west-1/prod/example/.terragrunt-cache/Y_shpyDtlnIaQFTYb9wiSoe22P8/06wdrOJD7Yl3z7ezhyFMJt6Gd1M/modules/aws/s3-bucket prefix=[/Users/alexgregory/.atlantis/repos/axxander/platform/3/default/terraform/aws/alexgregorydotio-prod/eu-west-1/prod/example] 
time=2023-04-11T10:46:14+01:00 level=error msg=Module /Users/alexgregory/.atlantis/repos/axxander/platform/3/default/terraform/aws/alexgregorydotio-prod/eu-west-1/prod/example has finished with an error: 1 error occurred:
	* exit status 1

 prefix=[/Users/alexgregory/.atlantis/repos/axxander/platform/3/default/terraform/aws/alexgregorydotio-prod/eu-west-1/prod/example] 
time=2023-04-11T10:46:14+01:00 level=info msg=
Initializing the backend...

Initializing provider plugins...
- Reusing previous version of hashicorp/aws from the dependency lock file
- Using previously-installed hashicorp/aws v4.62.0

Terraform has been successfully initialized!

You may now begin working with Terraform. Try running "terraform plan" to see
any changes that are required for your infrastructure. All Terraform commands
should now work.

If you ever set or change modules or backend configuration for Terraform,
rerun this command to reinitialize your working directory. If you forget, other
commands will detect it and remind you to do so if necessary.
╷
│ Error: configuring Terraform AWS Provider: IAM Role (arn:aws:iam::912142350009:role/TerragruntRole) cannot be assumed.
│ 
│ There are a number of possible causes of this - the most common are:
│   * The credentials used in order to assume the role are invalid
│   * The credentials do not have appropriate permission to assume the role
│   * The role ARN is not valid
│ 
│ AWS Error: operation error STS: AssumeRole, https response error StatusCode: 403, RequestID: 54633098-80aa-4828-bffa-5b5d14b3c7ba, api error AccessDenied: User: arn:aws:sts::912142350009:assumed-role/TerragruntRole/alex.gregory is not authorized to perform: sts:AssumeRole on resource: arn:aws:iam::912142350009:role/TerragruntRole
│ 
│ 
│   with provider["registry.terraform.io/hashicorp/aws"],
│   on provider.tf line 2, in provider "aws":
│    2: provider "aws" {
│ 
╵
time=2023-04-11T10:46:14+01:00 level=error msg=Terraform invocation failed in /Users/alexgregory/.atlantis/repos/axxander/platform/3/default/terraform/aws/alexgregorydotio-prod/eu-west-1/prod/example/.terragrunt-cache/Y_shpyDtlnIaQFTYb9wiSoe22P8/06wdrOJD7Yl3z7ezhyFMJt6Gd1M/modules/aws/s3-bucket prefix=[/Users/alexgregory/.atlantis/repos/axxander/platform/3/default/terraform/aws/alexgregorydotio-prod/eu-west-1/prod/example] 

time=2023-04-11T10:46:14+01:00 level=error msg=1 error occurred:
	* exit status 1





@axxander
Copy link
Owner Author

atlantis plan

@axxander
Copy link
Owner Author

Ran Plan for dir: terraform/aws/alexgregorydotio-prod workspace: default

Plan Error

Show Output
running "terragrunt run-all plan -input=false" in "/Users/alexgregory/.atlantis/repos/axxander/platform/3/default/terraform/aws/alexgregorydotio-prod": exit status 1: running "terragrunt run-all plan -input=false" in "/Users/alexgregory/.atlantis/repos/axxander/platform/3/default/terraform/aws/alexgregorydotio-prod": 
time=2023-04-11T10:53:33+01:00 level=info msg=The stack at /Users/alexgregory/.atlantis/repos/axxander/platform/3/default/terraform/aws/alexgregorydotio-prod will be processed in the following order for command plan:
Group 1
- Module /Users/alexgregory/.atlantis/repos/axxander/platform/3/default/terraform/aws/alexgregorydotio-prod/eu-west-1/prod/example



Initializing the backend...

Initializing provider plugins...
- Reusing previous version of hashicorp/aws from the dependency lock file
- Using previously-installed hashicorp/aws v4.62.0

Terraform has been successfully initialized!

You may now begin working with Terraform. Try running "terraform plan" to see
any changes that are required for your infrastructure. All Terraform commands
should now work.

If you ever set or change modules or backend configuration for Terraform,
rerun this command to reinitialize your working directory. If you forget, other
commands will detect it and remind you to do so if necessary.

Planning failed. Terraform encountered an error while generating this plan.

╷
│ Error: configuring Terraform AWS Provider: IAM Role (arn:aws:iam::912142350009:role/TerragruntRole) cannot be assumed.
│ 
│ There are a number of possible causes of this - the most common are:
│   * The credentials used in order to assume the role are invalid
│   * The credentials do not have appropriate permission to assume the role
│   * The role ARN is not valid
│ 
│ AWS Error: operation error STS: AssumeRole, https response error StatusCode: 403, RequestID: f99271e1-58eb-420e-873b-d144549a0c37, api error AccessDenied: User: arn:aws:sts::912142350009:assumed-role/TerragruntRole/alex.gregory is not authorized to perform: sts:AssumeRole on resource: arn:aws:iam::912142350009:role/TerragruntRole
│ 
│ 
│   with provider["registry.terraform.io/hashicorp/aws"],
│   on provider.tf line 2, in provider "aws":
│    2: provider "aws" {
│ 
╵
time=2023-04-11T10:53:38+01:00 level=error msg=Terraform invocation failed in /Users/alexgregory/.atlantis/repos/axxander/platform/3/default/terraform/aws/alexgregorydotio-prod/eu-west-1/prod/example/.terragrunt-cache/Y_shpyDtlnIaQFTYb9wiSoe22P8/06wdrOJD7Yl3z7ezhyFMJt6Gd1M/modules/aws/s3-bucket prefix=[/Users/alexgregory/.atlantis/repos/axxander/platform/3/default/terraform/aws/alexgregorydotio-prod/eu-west-1/prod/example] 
time=2023-04-11T10:53:38+01:00 level=error msg=Module /Users/alexgregory/.atlantis/repos/axxander/platform/3/default/terraform/aws/alexgregorydotio-prod/eu-west-1/prod/example has finished with an error: 1 error occurred:
	* exit status 1

 prefix=[/Users/alexgregory/.atlantis/repos/axxander/platform/3/default/terraform/aws/alexgregorydotio-prod/eu-west-1/prod/example] 
time=2023-04-11T10:53:38+01:00 level=info msg=
Initializing the backend...

Initializing provider plugins...
- Reusing previous version of hashicorp/aws from the dependency lock file
- Using previously-installed hashicorp/aws v4.62.0

Terraform has been successfully initialized!

You may now begin working with Terraform. Try running "terraform plan" to see
any changes that are required for your infrastructure. All Terraform commands
should now work.

If you ever set or change modules or backend configuration for Terraform,
rerun this command to reinitialize your working directory. If you forget, other
commands will detect it and remind you to do so if necessary.
╷
│ Error: configuring Terraform AWS Provider: IAM Role (arn:aws:iam::912142350009:role/TerragruntRole) cannot be assumed.
│ 
│ There are a number of possible causes of this - the most common are:
│   * The credentials used in order to assume the role are invalid
│   * The credentials do not have appropriate permission to assume the role
│   * The role ARN is not valid
│ 
│ AWS Error: operation error STS: AssumeRole, https response error StatusCode: 403, RequestID: f99271e1-58eb-420e-873b-d144549a0c37, api error AccessDenied: User: arn:aws:sts::912142350009:assumed-role/TerragruntRole/alex.gregory is not authorized to perform: sts:AssumeRole on resource: arn:aws:iam::912142350009:role/TerragruntRole
│ 
│ 
│   with provider["registry.terraform.io/hashicorp/aws"],
│   on provider.tf line 2, in provider "aws":
│    2: provider "aws" {
│ 
╵
time=2023-04-11T10:53:38+01:00 level=error msg=Terraform invocation failed in /Users/alexgregory/.atlantis/repos/axxander/platform/3/default/terraform/aws/alexgregorydotio-prod/eu-west-1/prod/example/.terragrunt-cache/Y_shpyDtlnIaQFTYb9wiSoe22P8/06wdrOJD7Yl3z7ezhyFMJt6Gd1M/modules/aws/s3-bucket prefix=[/Users/alexgregory/.atlantis/repos/axxander/platform/3/default/terraform/aws/alexgregorydotio-prod/eu-west-1/prod/example] 

time=2023-04-11T10:53:38+01:00 level=error msg=1 error occurred:
	* exit status 1





@axxander
Copy link
Owner Author

atlantis plan

@axxander
Copy link
Owner Author

Ran Plan for project: prod dir: terraform/aws/alexgregorydotio-prod workspace: default

Show Output
time=2023-04-11T11:00:49+01:00 level=info msg=The stack at /Users/alexgregory/.atlantis/repos/axxander/platform/3/default/terraform/aws/alexgregorydotio-prod will be processed in the following order for command plan:
Group 1
- Module /Users/alexgregory/.atlantis/repos/axxander/platform/3/default/terraform/aws/alexgregorydotio-prod/eu-west-1/prod/example



Initializing the backend...

Initializing provider plugins...
- Reusing previous version of hashicorp/aws from the dependency lock file
- Using previously-installed hashicorp/aws v4.62.0

Terraform has been successfully initialized!

You may now begin working with Terraform. Try running "terraform plan" to see
any changes that are required for your infrastructure. All Terraform commands
should now work.

If you ever set or change modules or backend configuration for Terraform,
rerun this command to reinitialize your working directory. If you forget, other
commands will detect it and remind you to do so if necessary.

Terraform used the selected providers to generate the following execution
plan. Resource actions are indicated with the following symbols:
  + create

Terraform will perform the following actions:

  # aws_s3_bucket.this will be created
  + resource "aws_s3_bucket" "this" {
      + acceleration_status         = (known after apply)
      + acl                         = (known after apply)
      + arn                         = (known after apply)
      + bucket                      = (known after apply)
      + bucket_domain_name          = (known after apply)
      + bucket_prefix               = (known after apply)
      + bucket_regional_domain_name = (known after apply)
      + force_destroy               = false
      + hosted_zone_id              = (known after apply)
      + id                          = (known after apply)
      + object_lock_enabled         = (known after apply)
      + policy                      = (known after apply)
      + region                      = (known after apply)
      + request_payer               = (known after apply)
      + tags_all                    = (known after apply)
      + website_domain              = (known after apply)
      + website_endpoint            = (known after apply)
    }

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

Changes to Outputs:
  + bucket_name = (known after apply)

─────────────────────────────────────────────────────────────────────────────

Note: You didn't use the -out option to save this plan, so Terraform can't
guarantee to take exactly these actions if you run "terraform apply" now.
time=2023-04-11T11:00:54+01:00 level=info msg=
Initializing the backend...

Initializing provider plugins...
- Reusing previous version of hashicorp/aws from the dependency lock file
- Using previously-installed hashicorp/aws v4.62.0

Terraform has been successfully initialized!

You may now begin working with Terraform. Try running "terraform plan" to see
any changes that are required for your infrastructure. All Terraform commands
should now work.

If you ever set or change modules or backend configuration for Terraform,
rerun this command to reinitialize your working directory. If you forget, other
commands will detect it and remind you to do so if necessary.
  • ▶️ To apply this plan, comment:
    • atlantis apply -p prod
  • 🚮 To delete this plan click here
  • 🔁 To plan this project again, comment:
    • atlantis plan -p prod
Plan: 1 to add, 0 to change, 0 to destroy.
  • ⏩ To apply all unapplied plans from this pull request, comment:
    • atlantis apply
  • 🚮 To delete all plans and locks for the PR, comment:
    • atlantis unlock

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