This message was deleted.

Hey! Yeah we're very wary of the plan file containing secrets and that's why the infracost CLI doesn't send the whole plan.json to the API. The CLI first extracts only the values that it needs to get unique price points before sending that upstream. So it only sends things like the instance type, region, operating system, etc. We have an example here (https://www.infracost.io/docs/faq#what-data-is-sent-to-the-cloud-pricing-api).

ok, that's great, I miss that point then, thank you for your answer

@billions-application-10929 I’m curious what gave you that initial impression? the CLI register, the getting started docs page, or something else? I’m wondering how we can better communicate this

How did I get to that question? Here is my reasoning: To be able to estimate the costs I need to use the

infracost

cli which obviously does not make any calculation on the client side, that's why I needed to register myself, to allow the cli to communicate to a remote API That means that my plan.json file, which is provided as an input of the

infracost

cli is (directly?) send to the remote api for calculating the costs On the docs, or landing page of the website, I did not see any information / or schema indicating that the cli is processing the plan file before sending it to the remote API

Thanks @billions-application-10929! that’s awesome feedback, I’ve made a note of it for future docs updates; this has come-up a few times

maybe in the getting started guide as people run brew install etc? This is great feedback, thanks Kevin!