#atlantis (2024-12)

Atlantis does not know about those Atmos settings

@jose.amengual can provide you with more info on how to use Atlantis with Atmos

no, it does not @Alcp

@Andriy Knysh (Cloud Posse) I believe this map is not a free map, right ?

config_templates:
      config-1:
        version: 3
        automerge: true
        delete_source_branch_on_merge: true
        parallel_plan: true
        parallel_apply: true
        allowed_regexp_prefixes:
          - automation/
          - dev/
          - qa/
          - staging/
          - prod/

any suggestions on how to manage the dependent items first

same with this:

project_templates:
      project-1:
        # generate a project entry for each component in every stack
        name: "{namespace}-{environment}-{component}"
        workspace: "{workspace}"
        dir: "{component-path}"
        terraform_version: v1.2.9
        delete_source_branch_on_merge: true
        apply_requirements:
          - "approved"
        autoplan:
          enabled: false
          when_modified:
            - "**/*.tf"
            - "$PROJECT_NAME.tfvars.json"

Ideally Atmos could allow to have a free map on those two settings butI’m not sure if that is possible

otherwise we will need Atmos code updates every time we add something to those file when we release new versions of Atlantis

@jose.amengual those are not free-form maps

so for order of execution is that something atlantis support?

yes

So basically we need to have a custom solution to generate the atlantis.yaml that creates the execution group

you can have Atmos generate the atlantis.yaml and after run another script that adds the depends on, that , until CloudPosse can integrate the newest atlantis aditions to the atlantis.yaml info the Atmos integration

ok that could work.. will try it

pre_workflow_hook

I have the script that generates the atlantis.yaml in the pre_workflow_hook with this setup, every first time we run atlantis plan we get this error

Ran Plan for dir: . workspace: default

Plan Error

running "terraform init -input=false -backend-config backends/$PROJECT_NAME.tf" in "/atlantis-data/repos/SIE/cratos/300/default": exit status 1: running "terraform init -input=false -backend-config backends/$PROJECT_NAME.tf" in "/atlantis-data/repos/SIE/cratos/300/default": 

Initializing the backend...
╷
│ Error: Failed to read file
│ 
│ The file "backends/.tf" could not be read.

when we run the atlantis plan again, it works again correctly .. not sure whats happens here

the problem is this : /default

your PR from Atmos uses a workspace other than default

so make sure the selection of the workspace happens correctly in Atlantis otherwise it will not see the files from the PR

Atlantis clones the PR on the Workspace repo

so it should look like

"/atlantis-data/repos/SIE/cratos/300/${{atmos.workspace}}"

We intend to make it a free form map, but we’re slammed with client work right now and not sure when we can get to it.

@Alcp if you want to take a look at the code, let us know. We also have a atmos-dev channel.

@jose.amengual wrt to the above error when I do atlantis plan the first time, the pre-workflow-hook get’s triggered and it generates the atlantis.yaml file in the default workspace, during this run atlantis plan ignores the atlantis.yaml file generated and just runs with default repo autodiscover mode.

The second time atlantis plan is run, this time it sees the atlantis.yaml already in the default workspace and works correctly. I disabled ATLANTIS_AUTODISCOVER_MODE=disabled this avoids the error but the behavior is same the first atlantis plan it doesn’t plan any projects but the second run of plan works correctly

do you have an atlantis.yaml committed to the repo?, or is always autogenerated?

for this kind of setups, autoplan is not very helful

there is a long oustanding issue in atlantis to improve the locks and add better support for workspaces that could avoid this issue

but no one to work on it. It requires Advance golang knowledge

atlantis.yaml is always autogenerated in our case, so the work around is to plan twice?

do you have an issue at git…

https://github.com/runatlantis/atlantis/issues/2538

btw the version I am using is v0.27.3 wrt automerge, after all applys are successful, the PR gets merged… my question here I don’t have automerge flags set anywhere in repo config or server config .. the default behavior is to merge?

no, is to do nothing, it will not automerge for you

https://github.com/runatlantis/atlantis/issues/260

https://github.com/runatlantis/atlantis/pull/4997

no, is to do nothing, it will not automerge for you but the behavior I am seeing is it auto merges after all applies are successful

and you do not have automerge enabled?

as a startup option maybe?

no I don’t have it at startup or at the repo or server config

I do not recall us setting that as default

do you have any other tool that could be doing that?

not really .. its merged by the atlantis github account

that is weird, I will have to check the changelog to see if we defaulted that to true