Helooo everyone! 🥳 We’ve just released Infracost v0.10.22, and it’s packed with some goodies! 🚀 One of the highlights is the new table output for the

diff

command! 👀

──────────────────────────────────
Infracost estimate: monthly cost will increase by $350 (+29%) ↑

┏━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━┳━━━━━━━━━━━━┳━━━━━━━━━━━━┳━━━━━━━━━━━━━━━━━┓
┃ Project                                                          ┃ Previous   ┃ New        ┃ Diff            ┃
┣━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━╋━━━━━━━━━━━━╋━━━━━━━━━━━━╋━━━━━━━━━━━━━━━━━┫
┃ infracost/infracost/cmd/infraco...ith_config_file_compare_to/dev ┃       $462 ┃       $252 ┃ -$210.24.       ┃
┃ infracost/infracost/cmd/infraco...th_config_file_compare_to/prod ┃       $743 ┃     $1,303 ┃ +$561 (+75%)    ┃
┗━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━┻━━━━━━━━━━━━┻━━━━━━━━━━━━┻━━━━━━━━━━━━━━━━━┛

New stuff! 🎉 - 🌟 Added table output to

diff

command! - 🌟 Added support for

azure_servicebus_namespace

resource - 🌟 Added support for

azurerm_logic_app_standard

resource Enhancements and Fixes 🔧 - 🐳 Example Wolfi Dockerfiles are now available - 🩹 Fixed various issues, including pricing and log level behaviour Give the new release a try and let us know what you think! We always appreciate your feedback and support! 💌 Happy cost-estimating! 💰📉

Hello GitLab users 🦊 👋. We’re working on making our GitLab integration even simpler by building an integration directly into Infracost Cloud, and we’d really appreciate some community input to help us choose the best way to connect with GitLab. Here are the two options we’re considering: Option 1: OAuth Connection • Can be setup by clicking straight from Infracost Cloud to authenticate with your GitLab account. • Linked to a specific user account, so it’s a good idea to set it up for a bot user Option 2: Access Tokens • You’ll need to create these in GitLab beforehand and then add them into Infracost Cloud. GitLab offers different types depending on your plan: ◦ 1. Personal Access Tokens - Available for all GitLab plans. These would need a long expiry to make sure the integration doesn’t break. These are tied to a specific user account, so it’s better to use a bot user for this too. ◦ 2. Group Access Tokens - Only available for those with self-hosted, Premium, or Ultimate plans. These create a separate bot user and don’t depend on a specific user account. These would also need a long expiry set up. We’d love to hear your thoughts on this! If anyone could provide some feedback for the following questions, that would be greatly appreciated 🙏 1. Which option works better for you? You can reply with a 1️⃣ or a 2️⃣ emoji, but it would be helpful to get some more information as well as to why. 2. What GitLab plan are you currently using (Free, Premium, Ultimate, self-managed or not) 3. Any other ideas or suggestions on this topic?

hey guyz

getting started with infrocost opensource projects

Hi all, we’re hiring at Infracost! 🚀 We have two key roles open: Customer Success Engineer and Software Engineer (Customer Success). Your role will be vital in helping our customers during proof-of-concepts, onboarding, deployment, and configuration of our platform. If you’re technically skilled and are passionate about customer success, we’d like to hear from you. Check out the roles and apply here: https://infracost.io/join-the-team If you have any questions about the role, or want to chat, please reach out to me at alistair@infracost.io 🙏

Hi Alistair. Nice to meet you. I am a senior full stack engineer and by any chance, I got to know about your company and company opening (software engineer). So I read your JD very carefully and I thought that this position is a good match for me.

I visited your web sites and considered your product. It has a strong potential to grow up rapidly. I want to join this wonderful company indeed.

Hi Infracost Team, We are using Infracost graphql API to get the resource usage for our multi cloud usage. Usecase i am looking at is being fulfilled with the resource level, but curious how to find the ingress/egress data cost between/across cloud service providers(GCP,AWS, Azure). Is there a way to query the egress resource costing from the graphql?

Hi! Does infracost publish their IP cidrs? (our org github is locked down behind an ip whitelist)

Hi Team, when running infracost auth login command after installing terracost. I am getting the below error.

Can someone help me with this?

@little-author-61621, can you please help me with the above issue

📣 Our June update blog is here, in addition to lots of bug fixes and new resources, there’s also: - 🚀 GitLab App: Quickly add Infracost to all of your GitLab repos with a few clicks - ✅ Jira App: Review & approve costs in Jira - 🧑‍💻 New VSCode extension with support for Config and Usage files - 📀 Export cost estimates to AWS S3 & Azure Blob Storage Oh, we’re also hiring! Thank you everyone for reporting issues, sending PRs, and providing feedback 🙇

Hey everyone! Me and @white-airport-8778 are at FinOps X in San Diego this week. If you are around, let's meet up!

📣 Hi everyone! Infracost v0.10.23 has been released! We’ve put a lot of effort into squashing some bugs for this one, so this release includes a lot fixes for different resources, plus general fixes to the HCL parsing logic 🐛🔨. One of the big fixes here is better support for

data.aws_availability_zones

blocks when Infracost parses the Terraform. We now mock these in a much nicer way so they work well if you’ve got a resource that loops over a lot of availability zones. infraheart Thank you everyone who has helped us by reporting and reproducing these issues.

We are doing some test on infracost using Githubaction.

but we are facing some issue.

we are expecting output like this

but we are not getting.

image.png

Hey all - we are now nearly 1,000 strong in this chat! We are shifting FinOps left - being proactive is super important! In the engineering workflow before we spend money. This group here (+ 3,500 companies now using Infracost!) is leading the industry 🎉 Super excited! https://shiftmag.dev/finops-906/

📣 Hi everyone! Infracost v0.10.25 has been released! This release contains a lot of functionality to integrate with the new Infracost Cloud Tagging Policies! This enables you to define your tagging policies so you can communicate and enforce the required tag keys/values in pull requests. You can find out more about this feature here: https://www.infracost.io/docs/infracost_cloud/tagging_policies/ We’ve also released a bunch of fixes. Thank you everyone who has helped us by reporting and reproducing issues. infraheart Here’s a screenshot of the Tagging Policies looks in your pull requests:

FYI GitHub is having an issue with new App installations (https://github.com/orgs/community/discussions/61291). They’re working on a fix, until then you won’t be able to install the Infracost GitHub App on new Infracost Cloud organizations. Existing apps continue to work fine.

Hi all, we’ve just released Infracost CLI v0.10.26 that fixes a regression introduced in v0.10.25. We recommend users to upgrade from v0.10.25 as soon as possible.

Hi, My name is kapila. I am new to infracost. Is any provision is available to push infra cost metrics directly to Kafka?

Hey folks, Hope you are all well. I have a delicious feature announcement! Tags can now be checked directly in the engineering workflow in CI/CD, before anything goes to production. Both the key and value can be verified. If the tagging policy has not been followed, your engineers will be notified in the PR and the code pull request can be blocked until it is fixed (that part is optional). This is now live, so feel free to log into Infracost Cloud, and define your tagging policies, and we will scan your repo and tell you how many resources are passing and failing your policy, along with details of each one. Then we track that over time: https://dashboard.infracost.io/ (if your trail period has expired, you can now extend it for another 14 days from the dashboard too). Any issues, please jump in the #help chat 💜

Good morning folks. I bet everyone woke up today, started making a coffee ☕️ then saw the Hashicorp announcement. Just wanted to tell everyone that this license change doesn't affect Infracost, and we are and will remain compliant going forward. We are one of Hashicorp's official partners too 👍🏽 Thanks for the love and support and the messages, it means a lot to me and the team ❤️ Back to building 🛠️

Alright, so ... cloud costs can sometimes be pretty dry, so I've decided I'm going to start posting memes to my twitt... I mean x.com lol (https://x.com/hassankhosseini) ...

📦 Infracost v0.10.29 Released In this release, our focus has been on enhancing Tag Policy support and delivering key optimizations and fixes. we’ve introduced a local CLI cache to boost the speed and efficiency of pricing lookups. Upgrading to this version should provide you with noticeable performance improvements. New Features ✨ - ✔️ Implemented a pricing client cache for improved performance by @hugorut. - ✔️ Support for applying tag policies to AWS launch templates by @hugorut. - ✔️ Added block device tags to AWS instance resources by @tim775. - ✔️ New region

il-central-1

added by @aliscott. Enhancements ⬆️ - ✔️ Enhanced data block functionality in submodules by @hugorut. - ✔️ Support for optional defaults added by @hugorut. - ✔️ Backoff retry logic included in comment handler by @hugorut. - ✔️ Conducted formatting adjustments by @tim775. Fixes 🛠️ - ✔️ Resolved race condition in terragrunt sources by @tim775. - ✔️ Fixed panic due to incorrect variable type definition by @hugorut. - ✔️ Resolved issues with invalid function arguments in mocking by @aliscott. - ✔️ Improved handling of un-Rel-able paths by @tim775. For the full list of changes, please see the Full Changelog. Thank you for being part of the Infracost community!

📣 Hey everyone! Our September update blog is live: • Tagging policy improvements: ◦ 1. Scan all repos for tagging issues ◦ 2. Sort by biggest issues ◦ 3. See a weekly progress chart • New email reports to summarize key changes across your repos • Major performance improvements for Terraform and Terragrunt repos • Many other CLI improvements