This message was deleted.
# atlantis-community
s
This message was deleted.
p
I do not think that is possible
a
There is an argument
-lock=false
that we can use, no?
p
but that is for all commands…..mmmmm wait
it is possible per project
in the atlantis.yaml I forgot about this
Copy code
- plan:
          extra_args: ["-lock", "false"]
repo_locking: false
is what you want
a
I understand that we can lock/unlock per step. What I want is multiple workflow where one workflow is just plan without lock and another workflow with plan with lock
p
this is exactly what that is
you will need to pass it per project
a
the project is the same
p
ahhhhh
so then you can do :
Copy code
workflows:
  myworkflow:
    plan:
      steps:
      - run: my-custom-command arg1 arg2
      - init
      - plan:
          extra_args: ["-lock", "false"]
      - run: my-custom-command arg1 arg2
    apply:
      steps:
      - run: echo hi
      - apply
but actually even if the project is the same
repo_locking: false
will work
because you do not care about lock on plan
only on apply
a
I do want to lock just before apply to prevent merge conflicts
p
just before apply? there is no state like that
is per command
a
So flow I want is: 1. PR created 2. Atlantis plan without locking 3. PR approved, merge checks pass 4. Atlantis plan with lock 5. Atlantis apply 6. PR merge 7. Atlantis unlocks
is that possible
p
that will only be possible if you pass the arg to the command
atlantis plan -lock=false
manually
a
gotcha
Thank you, appreciate this
p
you can’t do it that way at the workflow level