Hi, we are looking to do a POC on this tool as it looks great. Just a quick question, we use Azure Pipelines and we use variables to deploy our Iac

terraform plan -var 'geo=us' -var 'environment=ecos'

How can we build this into our pull requests to say env ecos cost X, env qa2 cost X, prod1 will cost X.

Hi @millions-plumber-38090 , You’d need to use a config file for something like this: https://www.infracost.io/docs/features/config_file/ for example, based on the information provided, your config file would look something like this:

version: 0.1

projects:
  - path: path/to/your/project
    name: ecos
    env:
      environment: ecos
      geo: us

  - path: path/to/your/project
    name: prod
    env:
      environment: prod
      geo: eu

Then it would be a matter of pointing infracost to that config file, e.g.

infracost breakdown --config-file infracost.yml

But, if you’re using GitHub as your repository, I’d recommend using our GitHub app to run your POC with. It’s much easier to iterate on an means you don’t have to define loads of boilerplate in your Azure pipelines. Hope this helps

Thanks Hugo, I did see the config file but wasn't sure how that would apply to us. I will have a go and reach out if we hit anymore issues.

👍

I am trying to set up the PR comment section now with an Azure pipeline but getting an error of

fatal: could not read Password for '<https://OrgName@dev.azure.com>': terminal prompts disabled

I am using the example provided here (https://github.com/infracost/infracost-azure-devops/tree/master/examples/multi-project-config-file) I copied and pasted as suggested by the documentation. I did also add the following in as suggested by some people.

- checkout: self
        persistCredentials: true

are you using azure repos or github?

Azure repos

what does your

infracost comment

command look like?

I am only using what is in the example provided for the whole pipeline.

that is using

github

Azure pipelines

yes but the example posts to github repo

ah okay, then its not even getting to that stage. As it fails on Checkout base branch

so this step:

# Clone the base branch of the pull request (e.g. main/master) into a temp directory.
      - bash: |
          branch=$(System.PullRequest.TargetBranch)
          branch=${branch#refs/heads/}
          git clone $(Build.Repository.Uri) --branch=${branch} --single-branch /tmp/base
        displayName: Checkout base branch

I found it, I was missing the following as the multi-project-config-file example didn't give the suggested option

--config http.extraheader="AUTHORIZATION: bearer $(System.AccessToken)

Sorry

was comment working in your pipeline before the

terraform_vars

change? I don’t think changing these parameters would have any affect on the comment posting logic?

Yes they were working fine beforehand the only change was from env to terraform_vars. It does seem very odd

so you managed to get a PR comment in your PR?

Yep if I use the following, works fine no problem

- path: env
    include_all_paths: true # include root and non-root modules
    name: POD - DELP
    env:
      environment: delp
      geo: us
      purpose: devqa

ok have you committed the updated infracost.yml into your main branch?

ah okay that could be it

it could be because of conflicts between the config files

That would make sense

don’t worry, that is confusing - and something that we’re not happy with. Sadly, all of this UX is fixed with the GH app, but we’re yet to get round to azure repos

That fixed it 🙂 thanks again

🚀

if we wanted to request a resource type to be added is it best to do a issue per resource request? e.g.

azurerm_windows_function_app

and

azurerm_route_table

yes please