This message was deleted.

atlantis plan -- -target=…

, see https://www.runatlantis.io/docs/using-atlantis.html#additional-terraform-flags

When using this option it still plans he whole env and not a particular resource

to pass flags to atlantis commands consider using this workflow (i've seen this in this chat some time ago, doubling it here)

workflows:
  terragrunt-default:
    plan:
      steps:
        - run:
            command: terragrunt init -input=false -upgrade
            output: hide
        - run:
            command: terragrunt plan -input=false -lock=false $(printf '%s' $COMMENT_ARGS | sed 's/,/ /g' | tr -d '\\') -out $PLANFILE
            output: hide
        - run: terragrunt show -no-color -json $PLANFILE > $SHOWFILE
        - run: terragrunt show $PLANFILE
    policy_check:
      steps:
        - policy_check:
            extra_args: ["-p", "/home/atlantis/policies/", "--all-namespaces", "--output=table", "--parser=json", "--no-color"]
    apply:
      steps:
        - run: terragrunt apply -input=false $(printf '%s' $COMMENT_ARGS | sed 's/,/ /g' | tr -d '\\') $PLANFILE
    import:
      steps:
        - env:
            name: TF_VAR_author
            command: 'git show -s --format="%ae" $HEAD_COMMIT'
        - run: terragrunt import -input=false $(printf '%s' $COMMENT_ARGS | sed 's/,/ /' | tr -d '\\')
    state_rm:
      steps:
        - run: terragrunt state rm $(printf '%s' $COMMENT_ARGS | sed 's/,/ /' | tr -d '\\')

will this allow to a targeted apply as well ?

there is a small issue here: you need to use

atlantis -plan --target

and it will create planfile with your target, after that you can run

atlantis apply

without target flag since you have targeted plan already but you can't instantly run

atlantis apply -- -target

because even with

target

flag it will apply the entire planfile, looks like terraform cant apply targeted plans 😞

in our local we use targeted plan using terraform . But using atlantis unable to do a targeted plan. It always does a full env plan

What if you try planning for a specific directory,

atlantis plan -d some-directory -- -target=my-resource

I did try with

atlantis plan -d some-directory -- -target=my-resource

it still does a full plan

yes you can pass flag here to https://www.runatlantis.io/docs/using-atlantis.html#examples

I have used resource targeting like this many times, are you sure it’s planning the whole project and not just the resource’ dependencies?

This is what I my atlantis.yml file look like

version: 3
projects:
- dir: providers/aws/us-east-1/dev
  apply_requirements: [approved, mergeable]
  terraform_version: v1.4.6
  workspace: default
  autoplan:
    when_modified: ["*.tf", "backends/*.tf"]
  workflow: tfversion1.4.6
- dir: providers/aws/us-east-1/test
  apply_requirements: [approved, mergeable]
  terraform_version: v1.4.6
  workspace: default
  autoplan:
    when_modified: ["*.tf", "backends/*.tf", "frontends/*.tf"]
  workflow: tfversion1.4.6
workflows:
  tfversion1.4.6:
    plan:
      steps:
        - run: /atlantis-data/bin/terraform1.4.6 init > /dev/null
        - run: /atlantis-data/bin/terraform1.4.6 plan >/dev/null -out plan.out
        - run: /atlantis-data/bin/terraform1.4.6 show plan.out
    apply:
      steps:
        - run: /atlantis-data/bin/terraform1.4.6 apply "plan.out"

you didn't fix the

tfversion1.4.6

workflow, so you can't pass the flags yet

If

-lock=false

is used then can multiple people plan and apply the same project ?

i use

-lock=false

with plans because sometimes it locks the project because of errors, and yes multiple people can do some plans at the same time at the same project but i don't recommend to use this in apply

Ok. Actually we have been using atlantis for sometime where in full env is planned and applied. But here only one person can work on a project and other is blocked. So looking for a way multiple people plan and apply on the same folder. I think multiple people working on the same project will corrupt the state file

they are defined on the atlantis level

How do we pass the values to these variables

$PLANFILE

and

$SHOWFILE

?

you don't need to pass it, it happens automatically

Ok. In my currently configuration I am explicitly using the file plan.out

it's up to you to use

$PLANFILE

and

$SHOWFILE

you didn't fix the

tfversion1.4.6

workflow, so you can't pass the flags yet

I did not understand this question of yours

in

tfversion1.4.6

there are no

$(printf '%s' $COMMENT_ARGS | sed 's/,/ /g' | tr -d '\\')

yeah, that could be the reason why I am not able to use target plan.

yes, but you can apply the targeted plan

I am confused here. I have this requirement where in Multiple people should be able to work on the same env. They should be able to do both plan and apply . Is this possible using targeted plan and apply suing custom workflow

yes, just add the

-lock=false

flag but i don't recommend to use it with applies because it potentially can lead to some disruptions

Okay

I think the bigger question here is why you need to use

-target

as a matter of course; in general, if you're using that all the time, you probably need to split up your Terraform roots (or you have a lot of drift you need to clean up).

There is a good reason why I used this in my case If I applied the changes at the same time I had some downtime since my pods were recreating That was the main reason to use target, to mitigate downtime

Yeah, I can see isolated use cases for it, but most of the time I've talked to people who are using it all the time, it's because either a) Terraform runs take forever (or hit API limits) because they have a zillion resources in the same root or b) they are afraid to apply the whole root because there's a bunch of changes that nobody knows what they will do or why they are there, both of which are...not great. Part of the reason I like Atlantis is that it forces people to make sure the map matches the territory on a regular basis.

I agree that makes sense :)