Does Atlantis have some built in limit on how many plans/apply's it can run?

I have a MR in gitlab, with 19 changes, but atlantis is only running a plan against 10 of them. I can see all 19 in the webhook that was sent to atlantis

Hello, I am new to atlantis. I followed the documentation and followed some youtube videos. My terraform application has a postgres backend. Where do I put the environment variables PGUSER and PGPASSWORD that the atlantis server can detect? I'm trying to investigate an issue we are having. I created the github webhook and we get a successful delivery (response:200), but the Atlantis actions do not appear on the PR AND when going to

<https://MY-SERVER.com/jobs/githook-id>

its an empty space (black box with nothing in it) so I don't even think

terraform init

is happening.

Hi I am pretty new to the Atlantis space and I am trying setup atlantis using this youtube vide but bootstrap doesnt seem to work, any ideas how I can go about it?

Hello, is Conftest the only policy check tool intended to integrate with Atlantis? My team relied on other tools like Cnspec until Atlantis

v0.24.0

rendered them incompatible. I created an issue tracking this, but I'm realizing Conftest is singled out as the only tool in the official documentation so I'm just looking for confirmation there

Hello! Just a QQ: does atlantis support terragrunt targetted plans/applies? It doesn't seem to atm (either that or I am doing something wrong. Thought best to ask first). If not, is there a timeline for this? Or is it similar to state_rm and imports where we have to hack around it for now?

<!here> I was unable to make Office Hours today, Please reach out via DM to either me or @PePe Amengual if you have any questions. Only thing to note is that we've applied for Atlantis to join CNCF and you can track the issue here: https://github.com/cncf/sandbox/issues/60

Hey all, I am trying to add atlantis import to my workflow. As I understand the documentation, I need only add the statement :

import_requirements:
      - approved

Is this correct?

Hi team! Quick question is anyone experiencing stack limit errors using the latest version released on the github repo? I’m using Atlantis running on ECS Since I upgraded I’m receiving this error:

Looking for help, can Paypal just to have someone to bounce ideas off of to figure this out. I have tried and tried, checked every dang tiny thing and my Atlas instance in ECS is still getting an i/o timeout when running plan in my PR and it tries to connect to the EKS cluster its modifying. It can post in PRs, init fine, and then plan timesout. Atlantis is in ECS fargate, my api cluster is on EKS. Checked AWS user, kube config, versioning, all the same as my local machine where it runs perfectly fine.

Thought it would might be helpful to someone at some point. After a bit of fighting, our Terragrunt instance now supports targetted plans/applies, state_rm, and imports:

plan:
  steps:
  - env:
      name: TERRAGRUNT_TFPATH
      command: 'echo "terraform${ATLANTIS_TERRAFORM_VERSION}"'
  - run:
      command: terragrunt plan -input=false $(printf '%s' $COMMENT_ARGS | sed 's/,/ /g' | tr -d '\\') -no-color -out $PLANFILE
      output: hide
  - run: |
      terragrunt show $PLANFILE
apply:
  steps:
  - env:
      name: TERRAGRUNT_TFPATH
      command: 'echo "terraform${ATLANTIS_TERRAFORM_VERSION}"'
  - run: terragrunt apply $PLANFILE
import:
  steps:
  - env:
      name: TERRAGRUNT_TFPATH
      command: 'echo "terraform${DEFAULT_TERRAFORM_VERSION}"'
  - env:
      name: TF_VAR_author
      command: 'git show -s --format="%ae" $HEAD_COMMIT'
  - run: terragrunt import -input=false $(printf '%s' $COMMENT_ARGS | sed 's/,/ /' | tr -d '\\')
state_rm:
  steps:
  - env:
      name: TERRAGRUNT_TFPATH
      command: 'echo "terraform${DEFAULT_TERRAFORM_VERSION}"'
  - run: terragrunt state rm $(printf '%s' $COMMENT_ARGS | sed 's/,/ /' | tr -d '\\')

Hello, I'm having some issues with the

checkout-strategy

and was hoping someone could provide a little insight as to what I might be doing wrong.

Hello, I'm curious about the expected behavior of Atlantis regarding which Terraform version to use. In our configuration we specify

default-tf-version: v1.0.9

in the config file but have

terraform {
  required_version = ">= 1.0"
}

in the Terraform. Should this result in version 1.0.9 of Terraform, or 1.5.7 (or whatever is currently the latest)? I'm unclear based on the docs. Thanks!

I've seen some mention of office hours, anyone have any details there?

Hello Hello, wondering if someone could help with an issue using bitbucket.org with the Terraform module for aws/ecs/fargate. Atlantis is deployed successfully and I can visit the site. when I make a new PR/comment on an existing PR I am getting 200 success responses from the webhook but atlantis doesn't do anything. The cloudwatch logs for ecs jst show health checks and "scheduled runtime memory gc". Nothing else stands out. Anyone have any ideas on where to look/what to check?? Specifics: • I have added a bitbucket app password called "atlantis" ◦ It doesn't show any date for "last accessed" so my assumption is the issue is around this but not sure how to check why it isn't being accessed • opened ingress/egress to public to eliminate any issues with network access • am using ssl with route53/acm

Hey all, Hoping to get some help with atlantis around what looks like

allow-fork-prs

we recently updated to v0.24.3 and when we run

atlantis plan

the plan is running against our master branch rather than our fork branch even though we have the

ATLANTIS_ALLOW_FORK_PRS=true

env variable set

Hey, I have a question about the configuration of the default workflow in atlantis: How can I set atlantis to run autoplan on a terraform workspace other than "default", without using atlantis.yaml file?

Hi!! How’re you people?!!! I’m new with Atlantis and i have this situation!! From local i’m using TF 1.5.7 and when i executed a plan, there no error.

Initializing provider plugins...
- Reusing previous version of hashicorp/random from the dependency lock file
- Reusing previous version of hashicorp/kubernetes from the dependency lock file
- Reusing previous version of hashicorp/google from the dependency lock file
- Reusing previous version of hashicorp/vault from the dependency lock file
- Reusing previous version of hashicorp/google-beta from the dependency lock file
- Using previously-installed hashicorp/google-beta v4.83.0
- Using previously-installed hashicorp/random v3.5.1
- Using previously-installed hashicorp/kubernetes v2.23.0
- Using previously-installed hashicorp/google v4.83.0
- Using previously-installed hashicorp/vault v3.20.1

Terraform has been successfully initialized!

But when Atlantis execute the plan in the same folder, i have this error:

Initializing provider plugins...
- Finding hashicorp/google versions matching "~> 3.53, >= 4.51.0, != 4.65.0, != 4.65.1, < 5.0.0"...
- Finding hashicorp/google-beta versions matching ">= 4.10.0, >= 4.51.0, != 4.65.0, != 4.65.1, < 5.0.0"...
- Finding hashicorp/random versions matching ">= 2.1.0"...
- Finding hashicorp/kubernetes versions matching "~> 2.10"...
- Installing hashicorp/google-beta v4.83.0...
- Installed hashicorp/google-beta v4.83.0 (signed by HashiCorp)
- Installing hashicorp/random v3.5.1...
- Installed hashicorp/random v3.5.1 (signed by HashiCorp)
- Installing hashicorp/kubernetes v2.23.0...
- Installed hashicorp/kubernetes v2.23.0 (signed by HashiCorp)
╷
│ Error: Failed to query available provider packages
│ 
│ Could not retrieve the list of available versions for provider
│ hashicorp/google: no available releases match the given constraints ~>
│ 3.53, >= 4.51.0, != 4.65.0, != 4.65.1, < 5.0.0

I tried add the version in required_version

terraform {
  required_providers {
    google = {
      source = "hashicorp/google"
      version = "4.83.0"
    }
  }
}

But doesn’t work!!!! Any tips to solve this?? Thanks a lot!!!!

Hi Everyone, Since yesterday we started facing the following issue with gitwebhooks to atlantis -

Hook executed successfully but returned HTTP 400 <!DOCTYPE html> <html lang=en> <meta charset=utf-8> <meta name=viewport content="initial-scale=1, minimum-scale=1, width=device-width"> <title>Error 400 (Bad Request)!!1</title> <style> *{margin:0;padding:0}html,code{font:15px/22px arial,sans-serif}html{background:#fff;color:#222;padding:15px}body{margin:7% auto 0;max-width:390px;min-height:180px;padding:30px 0 15px}* > body{background:url(//www.google.com/images/errors/robot.png) 100% 5px no-repeat;padding-right:205px}p{margin:11px 0 22px;overflow:hidden}ins{color:#777;text-decoration:none}a img{border:0}@media screen and (max-width:772px){body{background:none;margin-top:0;max-width:none;padding-right:0}}#logo{background:url(//www.google.com/images/branding/googlelogo/1x/googlelogo_color_150x54dp.png) no-repeat;margin-left:-5px}@media only screen and (min-resolution:192dpi){#logo{background:url(//www.google.com/images/branding/googlelogo/2x/googlelogo_color_150x54dp.png) no-repeat 0% 0%/100% 100%;-moz-border-image:url(//www.google.com/images/branding/googlelogo/2x/googlelogo_color_150x54dp.png) 0}}@media only screen and (-webkit-min-device-pixel-ratio:2){#logo{background:url(//www.google.com/images/branding/googlelogo/2x/googlelogo_color_150x54dp.png) no-repeat;-webkit-background-size:100% 100%}}#logo{display:inline-block;height:54px;width:150px} </style> <a href=//www.google.com/><span id=logo aria-label=Google></span></a> <p><b>400.</b> <ins>That's an error.</ins> <p>Your client has issued a malformed or illegal request. <ins>That's all we know.</ins>

Please help us to resolve the issue

Hello there 👋 Could this MR be reviewed and released, please: https://github.com/runatlantis/atlantis/pull/3747 That fixes an issue we`re also seeing in the latest Atlantis v0.25.0 release with GitLab 🙏

I’ve been getting this error recently a bunch if I plan a state explictly with

-d

before a general

atlantis plan

has already run: `atlantis plan -d foo-bar/baz`:

checking if workspace exists: stat /home/atlantis/.atlantis/repos/myorg/terraform/2348/default: no such file or directory

(I’ve confirmed that

foo-bar/baz

is a valid path / state).

Hi everyone!!! Is there any option that after a pr has been reviewed and approved, the apply is executed automatically instead of having to execute the atlantis apply? Thanks!!

Looking for help installing Atlantis on OpenShift. I added the HOME environment variable per the documentation. Got the following errors when applying the helm chart:

would violate PodSecurity "restricted:v1.24": allowPrivilegeEscalation != false (container "atlantis" must set securityContext.allowPrivilegeEscalation=false), unrestricted capabilities (container "atlantis" must set securityContext.capabilities.drop=["ALL"]), runAsNonRoot != true (pod or container "atlantis" must set securityContext.runAsNonRoot=true), seccompProfile (pod or container "atlantis" must set securityContext.seccompProfile.type to "RuntimeDefault" or "Localhost")

The following change fixed the issue, you may want to update the OpenShift install documentation

31 statefulSet: 232 annotations: {} 233 labels: {} 234 securityContext: 235 fsGroup: 1000690000 236 runAsUser: 1000690000 237 fsGroupChangePolicy: "OnRootMismatch" 238 priorityClassName: "" 239 updateStrategy: {} 240 # option to share process namespace with atlantis container 241 shareProcessNamespace: false

i've started noticing that the Gitlab Pipeline for

atlantis/apply

always shows the spinning blue circle, even once the apply is complete. why is that?

Hello, i searched everywhere without being able to found an answer to my question, so i hoped i could have an answer here. It's about command requirements. If my apply_requirement has • approved • mergeable Does my PR need to be approved AND mergeable to be able to apply, or it just needs to be approved OR mergeable ? Thank you in advance

Hello folks, we could use feedback on the proposed implementation to allow custom policy-checking tools other than Conftest. https://github.com/runatlantis/atlantis/pull/3765