This message was deleted.
# atlantis-community
s
This message was deleted.
b
I have added the value
checkout-strategy: merge
to a config file and use the --config when starting the server. However it seems to be ignoring that flag.
Copy code
$ cat /etc/atlantis/atlantis.yaml 
checkout-strategy: merge
checkout-depth: 1
enable-policy-checks: true
I have the following repo config
Copy code
- id: /.*/
      plan_requirements: [undiverged, mergeable]
      apply_requirements: [undiverged, mergeable, approved]
      allowed_overrides: [workflow]
and as you can see here it appears the checkout strategy is not being respected, I just wanted to make sure I'm not missing anything
This is using version 0.24.4
f
how do you run atlantis? I don't think it reads anything in /etc unless told to explicitly
b
we use the helm chart and run in it EKS, the helm chart does start the server with the
--config
flag pointing to that file
Copy code
containers:
    - name: atlantis
      args:
        - server
        - '--config=/etc/atlantis/atlantis.yaml'
f
undiverged and merge cannot be combined in a meaningful way I think - if undiverged is true, there cannot be anything to merge.
b
undiverged is broken atm anyhow https://github.com/runatlantis/atlantis/issues/3254 I was just trying anything 😄 I'll pull it back out
That's what lead us to trying to work on the checkout-strategy
ok so pulling that out gave me more what I was hoping for at least
I think I can live with this as that is what we want to prevent