-
Notifications
You must be signed in to change notification settings - Fork 0
Test PR for Atlantis #3
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
base: main
Are you sure you want to change the base?
Conversation
atlantis plan |
atlantis plan |
Plan Error
|
Plan Error
|
atlantis plan |
Plan Error
|
atlantis plan |
Ran Plan for dir: Plan Error
|
atlantis plan |
Ran Plan for dir: Plan Error
|
atlantis plan |
Plan Error
|
atlantis plan |
Plan Error
|
atlantis plan |
1 similar comment
atlantis plan |
Ran Plan for dir: Plan Error
|
1 similar comment
Ran Plan for dir: Plan Error
|
atlantis plan |
Ran Plan for dir: Plan Error
|
atlantis plan |
Ran Plan for dir: Plan Error Show Output
|
atlantis plan |
Ran Plan for dir: Plan Error Show Output
|
atlantis plan |
Ran Plan for dir: Plan Error Show Output
|
atlantis plan |
Ran Plan for project: Show Outputtime=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.
|
No description provided.