đź‘‹Hi @abundant-king-51389 - thanks for the awesome feedback!
I created this issue to track the bug - feel free to subscribe for updates.
Re project names: are you using a config-file? We wondered about adding “name” or “labels” into that.
Re expiry: makes sense! @busy-agent-35515 had even planned for this when we were developing that feature. What expiry options do you have in mind? just “Number of days”?
đź‘€ 1
a
abundant-king-51389
03/09/2022, 1:55 AM
as mvp, just knowing the information will eventually vanish is fine. I don't imagine we'd use reports after 7 days right now
🙌 1
abundant-king-51389
03/09/2022, 1:57 AM
long-term, I guess I'd like reports to exist forever but only be accessible to people in my org
w
white-airport-8778
03/09/2022, 1:59 AM
yep, that’s the idea, the API-key login is our MVP until we introduce orgs and multi-users that bring the API keys together, allow rotation etc.
👍 1
a
abundant-king-51389
03/09/2022, 2:02 AM
I don't use a config file currently. I think it would be easier for us to specify this stuff using CLI arguments or env vars.
Our Terraform configurations don't necessarily know what project names they deploy to. So having to write that into a config file in the repo seems overly coupled.
w
white-airport-8778
03/09/2022, 2:04 AM
tru dat, your other comment with the example infracost CLI run made that clear with the metadata
👍 1
white-airport-8778
03/09/2022, 2:09 AM
Please subscribe to this issue for the expiry feature and this issue for metadata idea.