This message was deleted.

Hey rick

ah, is there a new docker version?

No but I think the example that you followed is incorrect

I'll wait it out then, thank you 🙂

For the updated example step, note the change directory step

Let me check, thank you @mysterious-teacher-68276!

I'm ccing @white-airport-8778 who can help you further (im actually away from the laptop at the moment)

Hi Rick, I just merged https://gitlab.com/infracost/infracost-gitlab-ci/-/merge_requests/41 - plz ping here if that doesn’t help…

I ran the my pipeline twice now, it passes.. says the comment is updated.. but I don't see the comment getting updated

@sparse-wire-75745 if you add

--behavior=new

to the

infracost comment

command, it posts a new comment each time a commit is pushed to the MR so it makes it easier to debug. If I understand it correctly, Infracost is now posting a comment on the MR, but it shows a 0 diff, and you expected to see a non-0 diff? Does expanding the “Infracost output” section of the MR comment show any diffs of usage-based resources?

Hey, I figured the problem

Nice! so we need to update our config-file example to:

cd /tmp/base
      infracost breakdown --config-file=${CONFIG_FILE} \
                          --format=json \
                          --out-file=infracost-base.json

    # Generate an Infracost diff and save it to a JSON file.
    - |
      cd -            <<<<<<<< this is what we need to add, correct?
      infracost diff --config-file=${CONFIG_FILE} \
                     --compare-to=/tmp/base/infracost-base.json \
                     --format=json \
                     --out-file=infracost.json

I will do it, thank you 🙂

In the top-level readme for the gitlab-ci repo, can you please also add

--behavior=update

to the infracost-comment command so it’s explicit? That helps users know what to change if

update

isn’t what they want… I think we do that in the config-file example but we forgot to do it in the main example

sure, I have just request repo access.. I think I need that to be able to raise an MR.

you should be able to fork and send a MR from your fork. That’s what previous contributors have done in that repo and other GitHub repos we have

let me try that

I think https://github.com/infracost/infracost-azure-devops/tree/master/examples/multi-project-config-file might need the same fix, in case you have a little bit more time to contribute. Regardless of that though thanks for helping 🙂 I’ll leave the MRs for Hugo to review tmrw (he’s in the UK timezone so it’s late their time).