Abhilash Sandupatla
05/09/2023, 6:01 AMno plan found at path "aws/r53/eks/production/traefik/public" and workspace "default"–did you run plan?
Can someone please help on it ?
I have deployed atlantis through helm charts in EKSDylan Page
05/10/2023, 4:19 PMMateus Sousa
05/12/2023, 1:01 PMShnaidman Shaul
05/13/2023, 11:06 AMPriyashree Shetty
05/13/2023, 6:04 PMterraform --version
within the podDavid Heward
05/15/2023, 9:54 AMPardeep Bhatt
05/16/2023, 1:35 PMterragrunt/terraform plan apply
commands, do anyone know where any improvement which they done on their side for atlantis to make it less cpu intensive.streets
05/16/2023, 5:43 PM{
"ATLANTIS_GITLAB_TOKEN": "glpat-xxxx-xxxx"
}
i have created a kubernetes secret from this secret via the csi driver.
i have used loadEnvFromSecrets
to load the secret as an env var for ATLANTIS_GITLAB_TOKEN
.
the pod crashloops on start with:
atlantis-0 atlantis Error: --gh-user/--gh-token or --gh-app-id/--gh-app-key-file or --gh-app-id/--gh-app-key or --gitlab-user/--gitlab-token or --bitbucket-user/--bitbucket-token or --azuredevops-user/--azuredevops-token must be set
so i edited the statefulset to use image: ubuntu:latest
just so i could keep the pod alive long enough to check the env var is there, and it is:
root@atlantis-0:/# env | grep ATLANTIS_GITLAB_TOKEN
ATLANTIS_GITLAB_TOKEN=glpat-xxxx-xxxxx
why does atlantis fail to start? i deployed atlantis via latest chart version
chart version 4.12.5
Bruno Schaatsbergen
05/16/2023, 8:15 PMJT
05/17/2023, 12:42 AMError: initializing server: error initializing github authentication transport: wrong number of installations, expected 1, found 0
JT
05/17/2023, 2:37 PMChastity Blackwell
05/17/2023, 7:33 PMimport
command with Atlantis, and it looks like it's adding \\
before every character in the imported terraform resource when it runs the command? Is that intentional? For example:
running "/home/atlantis/.atlantis/bin/terraform1.4.6 import \\m\\o\\d\\u\\l\\e\\.\\c\\o\\n\\f\\l\\u\\e\\n\\t\\_\\c\\l\\o\\u\\d\\_\\c\\l\\u\\s\\t\\e\\r\\_\\n\\o\\n\\p\\r\\o\\d\\_\\g\\c\\p\\_\\u\\s\\_\\c\\e\\n\\t\\r\\a\\l\\1\\.\\c\\o\\n\\f\\l\\u\\e\\n\\t\\_\\k\\a\\f\\k\\a\\_\\c\\l\\u\\s\\t\\e\\r\\.\\m\\a\\i\\n \\e\\n\\v\\-\\x\\m\\w\\8\\2\\1\\/\\l\\k\\c\\-\\6\\3\\5\\d\\q\\3"
Nathan Handler
05/17/2023, 8:40 PM{
"level": "info",
"ts": "2023-05-17T20:10:54.823Z",
"caller": "server/server.go:941",
"msg": "Atlantis started - listening on port 4141",
"json": {}
}
However, the web interface won't load and webhooks from GitHub time out. We do see a number of log entries similar to:
{
"level": "info",
"ts": "2023-05-17T20:15:38.576Z",
"caller": "server/server.go:1016",
"msg": "Apply Lock: {false 0001-01-01 00:00:00 +0000 UTC }",
"json": {}
}
They seem to occur more often if I attempt to re-load the web interface. But it can sometimes take 10+ minutes after Atlantis claims to have started listening before it is actually in a functional state (still trying to confirm whether my refreshing the web interface is actually causing those Apply Lock log lines and possibly speeding up the launch, as it anecdotally feels that way, almost as if it is working through some queue). We have disable-repo-locking: true
in our Atlantis config file. We are also using the default boltdb
(and not doing anything fancy at the moment to persist it across deployments). Curious if anyone else has experienced this and knows how to speed up the slow startup times.cpuspellcaster
05/17/2023, 10:48 PMPULL_URL
variable is not being set by Atlantis, but the docs indicate that it should provide the Pull Request PR. Incidentally, we're also attempting to use the PROJECT_NAME
variable, and that value is being set, so it doesn't appear to be a scoping issue??ross strickland
05/18/2023, 2:15 PMAiman Ismail
05/19/2023, 5:44 AMPriyashree Shetty
05/20/2023, 4:59 PMstreets
05/22/2023, 9:43 AMGitHub
05/22/2023, 3:43 PMSeth Floyd
05/22/2023, 8:23 PMdefault
workspace?JT
05/23/2023, 3:40 AMworkflows:
staging:
plan:
steps:
- run: echo "INDIVIDUAL COMMENT"
- init:
extra_args: [-backend-config=staging.backend.tfvars]
- plan:
extra_args: [-var-file=staging.tfvars]
Then add that output as another separate commentGitHub
05/23/2023, 4:06 AMRB
05/23/2023, 4:08 AMAlberto Rojas
05/23/2023, 12:19 PMjwr
05/23/2023, 1:47 PMJT
05/23/2023, 2:52 PMATLANTIS_MARKDOWN_TEMPLATE_OVERRIDES_DIR
single_project_plan_success.tmpl:
## everything is the same as in main branch and then at bottom adding this
# TF Terragrunt Path
```diff
{{ .Env.TERRAGRUNT_TFPATH }}
```
repo.yaml:
repos:
- id: "/.*/"
workflow: terragrunt
workflows:
terragrunt:
plan:
steps:
- env:
name: TERRAGRUNT_TFPATH
command: 'echo "terraform${ATLANTIS_TERRAFORM_VERSION}"'
- run: terragrunt plan -input=false -out=$PLANFILE
- run: terragrunt show -json $PLANFILE > $SHOWFILE
JT
05/23/2023, 7:50 PMautomerge
is set to true here but is not working, anyone know why that would be? project ran applied successfully
atlantis.yaml
version: 3
automerge: true
delete_source_branch_on_merge: true
parallel_plan: true
parallel_apply: true
projects:
- name: 'project-dev'
dir: ./server/
workflow: normal
terraform_version: v1.4.6
autoplan:
enabled: true
when_modified: ["**/*.tf"]
workflows:
normal:
plan:
steps:
- init
- plan
JT
05/23/2023, 10:57 PM│ Error: Failed to read the given file as a state or plan file
│
│ State read error: Error reading
│ /atlantis/repos/<ORG NAME>/<REPO NAME>/9/default/directory/project-dev/directory/project-dev-default.tfplan
│ as a statefile: 2 problems:
│
│ - Unsupported state file format: The state file could not be parsed as
│ JSON: syntax error at byte offset 1.
│ - Unsupported state file format: The state file does not have a "version"
│ attribute, which is required to identify the format version.
│
│ Plan read error: plan file was created by Terraform 1.4.6, but this is
│ 1.4.5; plan files cannot be transferred between different Terraform
│ versions
╵
error when parsing input: unexpected end of JSON input
I've set the version in both atlantis.yaml
as well as in the backend code like this:
terraform {
required_version = "~> 1.4.6"
}
My understanding is that atlantis should see either of these and download the appropriate version of terraform.GitHub
05/24/2023, 1:21 PMEd
05/24/2023, 1:49 PM0.22.3
to 0.24.0
we started seeing sporadic errors like the one below
dir ".tmp/dev/my-service/infra" does not exist
files in this directory are rendered during pre_workflow_hook
step and atlantis.yaml looks like
version: 3
projects:
- dir: .tmp/dev/my-service/infra
...
Error usually happens when PR has 20+ plans and works with under 10 plans.
We’ll check version by version but maybe anyone has ideas what might be causing it 🙏