🤔 it seems that it doesn't pick it from the PR description, what if I add it in a message?

terrateam plan

terrateam plan

No Matching Changes ✖️

There are no matching changes to plan.

To plan all changes, comment:

terrateam plan

terrateam plan

Plans 👍

Outputs can be viewed in the Terrateam Console here.

Terrateam Plan Output 👍

Terraform used the selected providers to generate the following execution
plan. Resource actions are indicated with the following symbols:
+   create

Terraform will perform the following actions:

  # null_resource.drift[0] will be created
+   resource "null_resource" "drift" {
+       id = (known after apply)
    }

  # null_resource.drift[1] will be created
+   resource "null_resource" "drift" {
+       id = (known after apply)
    }

  # module.dev.null_resource.this[0] will be created
+   resource "null_resource" "this" {
+       id = (known after apply)
    }

Plan: 3 to add, 0 to change, 0 to destroy.

To apply all these changes, comment:

terrateam apply

terrateam plan '*'

No Matching Changes ✖️

There are no matching changes to plan.

To plan all changes, comment:

terrateam plan

terrateam plan 'dir:dev'

No Matching Changes ✖️

There are no matching changes to plan.

To plan all changes, comment:

terrateam plan

terrateam apply dir:env

No Matching Changes ✖️

There are no matching changes that are pending apply.

To apply all pending applies, comment:

terrateam apply

terrateam apply-foce dir:env

Unknown Command ✖️

Unknown command, see the list of valid commands below.

List of Terrateam commands:

• terrateam plan - Perform a plan command across all changes.
• terrateam plan <tag_query> - Perform a plan command across only those changes which match the tag query.
• terrateam apply - Perform an apply command across all changes.
• terrateam apply <tag_query> - Perform an apply command across only those changes which match the tag query.
• terrateam apply-force - Run an apply even if the change has not passed apply requirements.
• terrateam apply-force <tag_query> - Run an apply even if the change has not passed apply requirements across only those changes which match the tag query.
• terrateam apply-autoapprove - Performs a plan and apply it in the same execution.
• terrateam apply-autoapprove <tag_query> - Perform a plan and apply it in the same execution across only those changes which match the tag query.
• terrateam gate approve <token1> <token2> ... <tokenN> - Approve a gate.
• terrateam repo-config - Output the evaluated repository configuration as Terrateam, including config builder and indexer outputs incorporated in it.
• terrateam unlock - Release any locks this pull request owns. Useful for getting out of a sticky situation.
• terrateam unlock <pull requests number> - Release any locks owned by the listed pull requests.
• terrateam feedback <msg> - Give use feedback.

For help see:

https://terrateam.io/docs

terrateam apply dir:dev

No Matching Changes ✖️

There are no matching changes that are pending apply.

To apply all pending applies, comment:

terrateam apply

terrateam apply-force dir:dev

No Matching Changes ✖️

There are no matching changes that are pending apply.

To apply all pending applies, comment:

terrateam apply

Clearly it needs the file to be changed in any way 😞 I suppose it's a good thing.

While at it, I'd like to see if it works by adding commands to a comment, like this:

terrateam plan