#atlantis (2024-03)

I keep getting errors similar to the following when ‘terragrunt plan’ is being run in parallel in the atlantis pipeline.

• registry.terraform.io/hashicorp/aws: there is no package for registry.terraform.io/hashicorp/aws 4.67.0 cached in .terraform/providers
• registry.terraform.io/hashicorp/aws: there is no package for registry.terraform.io/hashicorp/aws 4.63.0 cached in .terraform/providers
• registry.terraform.io/hashicorp/aws: the cached package for registry.terraform.io/hashicorp/aws 4.67.0 (in .terraform/providers) does not match any of the checksums recorded in the dependency lock file

These errors come at different projects during the ‘terragrunt init’ which gets executed as part of ‘terragrunt plan’

They appear to be happening due to the the terragrunt cache being accessed concurrently.

What is the typical solution to fix these issues when using the terragrunt workflow in atlantis?

v0.27.2 Maintainer Notes

Atlantis has submitted its application to CNCF! cncf/sandbox#60 Please +1 the issue to show your support. Atlantis will continue to use a new release…

:wave: I am trying to get adoption of Atlantis in my organization. I’ve got it set up, but there looks to be an issue with with the undiverged behavior that is preventing me from moving forward. An issue as in - it just flat doesn’t work. I have the following requirements set in my repo config:

plan_requirements: [undiverged]
apply_requirements: [approved, mergeable, undiverged]
import_requirements: [approved, mergeable, undiverged]

as I understand, the checkout strategy for undiverged also has to be set to merge, so I have changed that behavior as well:

ATLANTIS_CHECKOUT_STRATEGY: merge

I am also using GitHub.

In a PR that is behind the base branch (main), I type atlantis plan and the plan just plans when it shouldn’t. It also applies when it shouldn’t as well. There’s no checking going on that the branch is dirty and needs to be rebased. To troubleshoot, I dug around github issues and found https://github.com/runatlantis/atlantis/issues/4051, which has a very similar issue that I am experiencing. They suggested it might be due to parallel planning/applying, so I also disabled any parallelization around those actions. Unfortunately, without success.

Does this feature work at all?

For those that might be interested, Gitea/Forgejo support just got merged https://github.com/runatlantis/atlantis/commit/722c4a93727ffdeef13e9b911e062321a0df19b7

@here We had an amazing day at OpenTofu day at Kubecon , here is our talk https://youtu.be/Pm1cxFSwOEc