Differnt paths for infracost.json used in Azure DevOps documentation

[infracost]

Differnt paths for infracost.json used in Azure DevOps documentation

[joerg]

Not much trouble at all, no. We use Terrafrom to roll out Atlantis and have to inject the repo config via JSON as an Env variable... getting all the escapes right was much more confusing. :-D
So far it seems to work quite nice. I had problems with a disk type in Azure (some Premium) that seems to be unsupported by Infracost and always got "no cost estimate" which was confusing but well, theres always some weird things when you start using new tools.
The comment type for Azure DevOps seems to be wonky since I never get updates, neither in new comments as I would like to have nor with updated comments, but I am blaming Microsoft here. Azure DevOps really is quite buggy.

[vdmgolub]

@joerg Hello! Sorry about that :( Thank you for reporting and creating the issue! 🙏 True power of opensource :) 💪 We'll fix that.

Hopefully it didn't cause too much trouble. Apart from that, may I ask how you find the examples? Were you able to run Infracost successfully with your setup? Does it work as you expected? We are happy to receive any feedback as it helps us to improve things. :)

[vdmgolub]

@joerg Thank you very much! :) For the missing disk types feel free to open an issue, we currently have a bunch of those related to new Azure resources. Seeing people upvoting them helps to determine what we should add next. Or if you feel about doing some opensource, we welcome community contributions as well. :)

W/r/t comments, Azure Repos is different from GitHub, that's true, but the update behavior should work. It may be something about permissions (we're using their REST API to fetch and create/update comments), or maybe we have a bug :) The command outputs some logs, see this example, it may provide some context what happens.

We also have a community Slack. Please join if you still have any issues, we can help in realtime :)

[vdmgolub]

Checked all other examples, seems like this was the only typo. Fixed here: 3ea411f. @joerg Thank you for reporting! :)