https://infracost.io logo
Join Slack
Powered by
Hi guys, I’ve updated to 0.10.16 and get an error ...
# help
s
Hi guys, I’ve updated to 0.10.16 and get an error in VScode now in the debug log:
debug: setting context infracost:active to true
debug: setting context infracost:loggedIn to true
debug: initializing workspace
debug: running Infracost in project: /Users/jgrumboeck/git/redbullmediahouse/cp-cloud-terraform
debug: running Infracost breakdown
debug: found project redbullmediahouse/cp-cloud-terraform
debug: setting context infracost:error to undefined
The Infracost spinner in the lower right is just spinning and no costs are shown. Is this a known issue? The .infracost folder jsut holds an terraform_modules/manifest.json, which content is 
{"Modules":[]}
… so also quite empty.
m
hey johannes 👋
which version of vscode are you using?
*vscode-infracost
s
0.2.3
m
and vscode was working with the 
0.10.15
release?
s
Had 0.10.13 before … let me switch back or downgrade to 0.10.15
m
vscode should use an bundled infracost version though, so this is a bit wierd
s
Hmmm … sorry, is there a quick way how to switch to an older version of infracost with brew?
ok … uninstall infracost from brew, so the bundled version should be used by VScode right? Error is still the same.
m
hmm ok
@stocky-salesmen-15167 can I schedule a call with you tomorrow to go over this - would be helpful to be able to build specific binaries for your case to get to the bottom of the issue?
s
Sure.
m
I’m going to release a 
0.2.4
version with the latest CLI bundled and see if that does anything for you
bear with me
s
No worries, also not time critical.
m
👍
s
just send me an invite … if not possible time-wise I’ll respond with a different suggestion
m
cool thanks
s
Found it! Was my fault: I had an old 
<http://versions.tf|versions.tf>
in the root folder containing some valid 
terraform {}
stanza. This somehow mislead infracost to not being able to detect the multiprojects in this monorepo. I removed this old crap and now it works.
m
ah nice - we have improvements inbound for the next release so this won’t fail in your monorepo
I’ve just released v0.2.4 of the vscode extension btw
which has the new cli bundled
s
The new parallelism seems to overload TFC private registry API. Get some HTTP 429
m
damn
could you raise an issue for that
(can be brief, just so we can prioritise it)
s
Sure. Rerunning it helps.
m
thank you sir
s
Do you also need this “infracost breakdown --debug-report” json?
m
for the private registry bug?
s
jep
m
nah don’t worry
s
👍
Maybe we still could have a call as there are some numbers wrong in the vscode infracost tab I think.
27 Views
Open in Slack
PreviousNext
Powered by