Plan steps run with -lock=false

[Eugst]

Community Note

• Please vote on this issue by adding a 👍 reaction to the original issue to help the community and maintainers prioritize this request. Searching for pre-existing feature requests helps us consolidate datapoints for identical requirements into a single place, thank you!
• Please do not leave "+1" or other comments that do not add relevant new information or questions, they generate extra noise for issue followers and do not help prioritize the request.
• If you are interested in working on this issue or have submitted a pull request, please leave a comment.

---

• I'd be willing to implement this feature (contributing guide)

Describe the user story
I would like to have the opportunity to not lock after successful plan with custom run, for example:

workflows:
  wf1:
    plan:
      steps:
        - run: terragrunt run-all plan

Currently extra_args: ["-lock=false"] is only possible for steps init/plan, but not run.

Describe the solution you'd like

workflows:
  wf1:
    plan:
      steps:
        - run: terragrunt run-all plan
          extra_args: ["-lock=false"]

Describe the drawbacks of your solution

Describe alternatives you've considered
Any possible solution to make possible run custom plans without locks.

[jamengual]

But you can just pass that to the terragrunt command on the same run line.

[Eugst]

@jamengual thank you for your reply! do you mean like

workflows: wf1: plan: steps: - run: terragrunt run-all plan -lock=false

It will recognize as terragrunt parameter, isn't it? With any other command it will work the same?

[jamengual]

yes like that but I do not use terragrunt so maybe the order of the flag is important?

…

On Wed, Oct 11, 2023 at 10:46 AM Eugene Storchevoy ***@***.***> wrote: @jamengual <https://github.com/jamengual> thank you for your reply! do you mean like workflows: wf1: plan: steps: - run: terragrunt run-all plan -lock=false It will recognize as terragrunt parameter, isn't it? With any other command it will work the same? — Reply to this email directly, view it on GitHub <#3844 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAQ3ERH6SGKEDWHVD7OMCV3X63LORANCNFSM6AAAAAA534CILM> . You are receiving this because you were mentioned.Message ID: ***@***.***>

[Eugst]

Thanks @jamengual !
Let's say I have custom command:

run: echo "hello world!";

Where I need to put lock parameter?

[jamengual]

run command is basically running a one-liner on a shell.
so whatever is the correct way to add a parameter to your command, that is how you do it in the run command.

[Eugst]

@jamengual could you provide any example, please?

[jamengual]

- run: terraform plan -lock=false should work

[Eugst]

just tried tflint -lock=false
and got:

Failed to parse CLI options; `lock=false` is unknown option. Please run `tflint --help

kinda the same with help.

So back to the core of issue - I would to run custom command and if it's run successfully - make ability to not add the lock to the atlantis.

[jamengual]

you are confusing TF locks with atlantis locks, those are 2 different things.
you showed a terragrunt command before and that is a terrafrom level lock.

#2876