We did an ls -ltra on the directory to prove this ourselves and also attached the Pr comments.

in your pipeline you specify

diff

&

breakdown

with

--path

rather than

--config-file

2 secs

--- steps: - bash: | ssh-agent -a $(SSH_AUTH_SOCK) mkdir -p ~/.ssh echo "$(echo $GIT_SSH_KEY_BASE_64 | base64 -d)" | tr -d '\r' | ssh-add - ssh-keyscan ssh.dev.azure.com >> ~/.ssh/known_hosts displayName: Add GIT_SSH_KEY # condition: and(succeeded(), eq(variables['Build.Reason'], 'IndividualCI')) condition: and(succeeded(), eq(variables['Build.Reason'], 'PullRequest')) env: GIT_SSH_KEY_BASE_64: $(gitSshKeyBase64) # Install the Infracost CLI, see https://github.com/infracost/infracost-azure-devops#infracostsetup - task: InfracostSetup@1 displayName: Setup Infracost # condition: and(succeeded(), eq(variables['Build.Reason'], 'IndividualCI')) condition: and(succeeded(), eq(variables['Build.Reason'], 'PullRequest')) inputs: apiKey: $(infracostApiKey) # 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/} echo $branch mkdir $(Pipeline.Workspace)/s/$(Build.Repository.Name)/base git clone git@ssh.dev.azure.com:v3/MetroBank/Metro%20Cloud%20Platform/$(Build.Repository.Name) \ --branch=${branch} --single-branch "$(Pipeline.Workspace)/s/$(Build.Repository.Name)/base" displayName: Checkout base branch condition: and(succeeded(), eq(variables['Build.Reason'], 'PullRequest')) # condition: and(succeeded(), or( eq(variables['Build.Reason'], 'IndividualCI'), eq(variables['Build.Reason'], 'Manual')) # Generate an Infracost cost estimate baseline from the comparison branch, so that Infracost can compare the cost difference. - bash: | pwd ls -ltr mkdir $(Pipeline.Workspace)/s/$(Build.Repository.Name)/infracost-reports infracost breakdown --config-file $(Pipeline.Workspace)/s/$(Build.Repository.Name)/infracost.yml \ --format=json \ --out-file=$(Pipeline.Workspace)/s/$(Build.Repository.Name)/infracost-reports/infracost-base.json displayName: Generate Infracost cost estimate baseline workingDirectory: $(Pipeline.Workspace)/s/$(Build.Repository.Name)/base condition: and(succeeded(), eq(variables['Build.Reason'], 'PullRequest')) # condition: and(succeeded(), eq(variables['Build.Reason'], 'IndividualCI')) # Generate an Infracost diff and save it to a JSON file. - bash: | pwd ls -ltr infracost diff --config-file $(Pipeline.Workspace)/s/$(Build.Repository.Name)/infracost.yml \ --format=json \ --compare-to=$(Pipeline.Workspace)/s/$(Build.Repository.Name)/infracost-reports/infracost-base.json \ --out-file=$(Pipeline.Workspace)/s/$(Build.Repository.Name)/infracost-reports/infracost.json displayName: Generate Infracost diff workingDirectory: $(Pipeline.Workspace)/s/$(Build.Repository.Name) condition: and(succeeded(), eq(variables['Build.Reason'], 'PullRequest')) # condition: and(succeeded(), or( eq(variables['Build.Reason'], 'IndividualCI'), eq(variables['Build.Reason'], 'Manual')) - publish: '$(Pipeline.Workspace)/s/$(Build.Repository.Name)/infracost-reports' displayName: 'Publish reports' artifact: drop # Posts a comment to the PR using the 'update' behavior. # This creates a single comment and updates it. The "quietest" option. # The other valid behaviors are: # delete-and-new - Delete previous comments and create a new one. # new - Create a new cost estimate comment on every push. # See https://www.infracost.io/docs/features/cli_commands/#comment-on-pull-requests for other options. - bash: | infracost comment azure-repos --path=$(Pipeline.Workspace)/s/$(Build.Repository.Name)/infracost-reports/infracost.json \ --azure-access-token=$(System.AccessToken) \ --pull-request=$(System.PullRequest.PullRequestId) \ --repo-url=$(Build.Repository.Uri) \ --behavior=update displayName: Post Infracost comment condition: and(succeeded(), eq(variables['Build.Reason'], 'PullRequest')) # condition: and(succeeded(), or( eq(variables['Build.Reason'], 'IndividualCI'), eq(variables['Build.Reason'], 'Manual'))

i’m wondering if it’s getting an old artefact

what happens when you remove

- publish: '$(Pipeline.Workspace)/s/$(Build.Repository.Name)/infracost-reports'
        displayName: 'Publish reports'
        artifact: drop

step

Same results with or without this task

Another thing we noticed with InfraCost --path setting that does not make sense with config-file

as the config file just has a field for --path and can't be changed between calls

can you send me that infracost.json

Also a great idea to update your doc to use workingDirectory when using --config-file as this caught us out for a while. workingDirectory: $(Pipeline.Workspace)/s/$(Build.Repository.Name)/base workingDirectory: $(Pipeline.Workspace)/s/$(Build.Repository.Name) 🙂

and we do not see the different envs breakdown in the dashboard

message has been deleted

Strange, it's like it is not picking up the main resources at all from main.tf

only finding resources in the usage-file.yml

This fails silently so you wouldn't see this

Can I check that the path structure you've got is correct - where are you usage files in relation to the project

this is the ls from the root, they are stored in config/env/...

coffee time

give me a shout when your about and if you’re free to jump on a zoom to help debug this and get you to success

I’ve got meetings from 2:30pm (BST) to 4pm. So ill be free after that

first meeting is at 2:30pm (BST)

Sent