This message was deleted.

Hey @dry-football-79311 , we have a terragrunt example in our actions repository here: https://github.com/infracost/actions/tree/master/examples/terragrunt

ah cool thx

--path

can accept a directory too https://www.infracost.io/docs/features/cli_commands/#option-1-terraform-directory. This is a simplest way to start using Infracost 🙂

hey is there this script https://www.infracost.io/docs/troubleshooting/#terragrunt in github action ?

Hey! Unfortunately no, but you could copy-paste it in a separate step

@dry-football-79311 I’m curious if Infracost Terragrunt logic didn’t work for your use-case? That’s used in the GH example that Hugo mentioned, and it’s similar to what the troubleshooting bash script does (the bash script creates a config-file dynamically, to run infracost, then deletes it). I tweaked the docs to clarify this.

Actually the action that Vadim mentioned worked fine in my terragrunt repo. I was just trying to check whats happening under the hood 🙂

Sadly not at the moment, If you want to use the same token you used on a different machine e.t.c, you can pull it with:

infracost configure get api_key

then set it with

infracost configure set api_key ${token_from_before}

cool thx

which post

--behaviour

are you running with

infracost comment

with? If it’s

update

this will only create one comment and update it with costs as they change. If you want a new comment every time you can use

new

this is great thanks for the helpfull answers

no problem