Justin S
06/06/2023, 2:48 PMVijay Prakash
06/06/2023, 6:53 PMLaurens Vets
06/06/2023, 8:46 PMterragrunt.hcl
which reads a .yml
file in locals
to fill in inputs
. When the yaml file changes, it seems that Atlantis doesn’t want to run a plan? Any idea why that might be?Andre Ziviani
06/07/2023, 6:15 PMRafael Muller
06/09/2023, 3:42 PMrunning "/usr/local/bin/terraform init -input=false -upgrade" in "/atlantis-data/repos/rtmuller/azure-lab/9/default/atlantis3": exit status 1
Initializing the backend...
╷
│ Error: Error building ARM Config: please ensure you have installed Azure CLI version 2.0.79 or newer. Error parsing json result from the Azure CLI: launching Azure CLI: exec: "az": executable file not found in $PATH.
│
│
╵
Nour Eddine Rahou
06/12/2023, 11:21 AMAndrew Dionisio
06/13/2023, 1:27 PMThe dev_use1_test-app workspace at path dev/use1/test-app is currently locked by another command that is running for this pull request.
Wait until the previous command is complete and try again.
Andrew Dionisio
06/13/2023, 2:19 PM╷
│ Error: Failed to install provider
│
│ Error while installing hashicorp/aws v4.67.0: read tcp
│ [xxxx:xxxx:xxxx:xxxx:xxxx::1c]:48770->[xxxx:xxxx:xxxx:xxxx:5:xxxx:xxxx:xxxx]:443:
│ read: connection timed out
Justin S
06/13/2023, 7:54 PMPriyashree Shetty
06/14/2023, 6:58 AMDylan Page
06/14/2023, 3:28 PMTyler Allen
06/14/2023, 3:28 PMPePe Amengual
06/14/2023, 4:59 PMSeth Floyd
06/14/2023, 6:13 PMatlantis plan -d service/workflow -w dev
I get this error:
checking if workspace exists: stat /atlantis-data/repos/company/infrastructure/103/default: no such file or directory
Seth Floyd
06/14/2023, 6:14 PMPriyashree Shetty
06/15/2023, 8:20 AMatlantis plan -d dir.
.Plan output Plan: 0 to add, 0 to change, 3 to destroy.
I tried to run atlantis apply -d dir
to delete the s3 resource, but it is not deleting the s3 resource created. There is no build happening in the bitbucket PR for the atlantis apply
. Cannot we use atlantis for deleting the resource? This link https://github.com/runatlantis/atlantis/issues/563#issuecomment-478999912 says that we can delete the resource by deleting it from the config filenori
06/15/2023, 9:44 AMog f91
06/18/2023, 5:32 PMlocal_exec
in terraform to execute a script which contains "docker run", but when I apply from PR comment in bitbucket server, it shows this error:
docker: Got permission denied while trying to connect to the Docker daemon socket at unix:///var/run/docker.sock: Post "<http://%2Fvar%2Frun%2Fdocker.sock/v1.24/containers/create>": dial unix /var/run/docker.sock: connect: permission denied.
but the wired thing is I already gave the permission of docker, and I tried run terraform apply in the server where atlantis is deployed, using the atlantis user, the ``local_exec` can execute docker run(script is executed successfully), I have struggled with this for some time, do you have any suggestions on how to resolve it
fyi: atlantis is deployed as a systemd unit in a single node, and I created the 'atlantis' user and user group specifically for its executionKumaresan Periyasamy
06/19/2023, 12:07 AMRan Apply for 0 projects:
. When PR is created atlantis does auto plan and show the changes then when we tried to apply using atlantis apply.
if show applied for 0 projects , is anyone encountered similar issues ? and log show’s that plan file is missing
atlantis version: v0.23
workflows:
default:
plan:
steps:
- init:
extra_args: [ "-reconfigure"]
- run: TF_WORKSPACE=$WORKSPACE tflint --config /home/atlantis/.tflint.hcl
- plan
- run: terraform$ATLANTIS_TERRAFORM_VERSION show -no-color -json $PLANFILE > tfplan.json
- run: cp tfplan.json /tmp/$BASE_REPO_OWNER-$BASE_REPO_NAME-$PULL_NUM.json
apply:
steps:
- apply
Jason Reslock
06/20/2023, 3:43 PMapply_requirements: [approved,mergeable]
I have a PR that appears to have passed all of the required checks (plans fine, approvals from code owners, jenkins build passed, etc.) but atlantis will not apply it.
How can I debug why atlantis thinks the PR is not mergeable when github clearly thinks it is fine?Chad Bailer
06/20/2023, 5:34 PMRan Plan for 6 projects:
project: environments/dev02 dir: environments/dev02 workspace: default
project: environments/dev03 dir: environments/dev03 workspace: default
project: environments/dev04 dir: environments/dev04 workspace: default
project: environments/dev05 dir: environments/dev05 workspace: default
project: environments/dev06 dir: environments/dev06 workspace: default
project: environments/dev01 dir: environments/dev01 workspace: default
Haven't seen anyone discussing it so I'm curious if anyone has solved this before. It would look way cleaner if we always had the plan output in the same orderGitHub
06/20/2023, 10:05 PMLuiz Silva
06/20/2023, 11:17 PMterraform/my-aws-account/my-region/s3/my-bucket/terragrunt.hcl
And I will need to have relative paths that I need to have autoplan running.
Sometimes I will have this:
terraform/my-aws-account-a/us-east-1/s3/my-bucket-test/terragrunt.hcl
Or this:
terraform/my-aws-account-b/us-east-1/s3/my-bucket-test/terragrunt.hcl
My current atlantis.yaml:
version: 3
projects:
- dir: terraform/my-aws-account-a/us-east-1/s3/my-bucket-test
autoplan:
when_modified: ["*.hcl"]
enabled: true
How can I have only one dir and run multiple auto plans across all paths? I’ve tried to configure like this:
version: 3
projects:
- dir: terraform/*/*/*/*
autoplan:
when_modified: ["*.hcl"]
enabled: true
But did not workMichael Coombs
06/21/2023, 3:15 PMterraform-aws-atlantis
code as a standalone project, but getting the following ECS error:
ResourceInitializationError: unable to pull secrets or registry auth: execution resource retrieval failed: unable to retrieve secrets from ssm: service call has been retried 5 time(s): RequestCanceled: request context canceled caused by: context deadline exceeded. Please check your task network configuration.
any help or suggestions would be appreciated. thankswby
06/21/2023, 6:42 PMThe default workspace at path . is currently locked by another command that is running for this pull request.
Wait until the previous command is complete and try again.
is that expected? I don’t see any changes in the release notes that would seem to be related from a quick lookMaxime Valo
06/22/2023, 8:46 AMJT
06/23/2023, 3:14 PMJT
06/23/2023, 3:16 PMJT
06/24/2023, 1:06 PMproject_1
and project_2
inside. project_2
relies on the output from project_1
so it should only ever run afterwards.Luiz Silva
06/27/2023, 12:24 AM