This message was deleted.

Hi Keith! Compost is using CI's env vars to detect the environment. And apparently something is not set. We recently released commenting feature within the CLI binary, so you can already try the new

infracost comment gitlab

command. Here are examples how to use it: https://www.infracost.io/docs/features/cli_commands/#gitlab

yup! “compost” was our first iteration on comments for CI/CD systems but we’ve rolled that into

infracost comment

as Vadim mentioned so I would use the updated examples above - it should simplify things. We just merged the updated examples 5mins ago 😅

Giving it a try!

Awesome! 🚀

FYI, when the comment gets added and that gets relayed to Slack (with Gitlab Slack integration), it winds up looking like this:

that Slack message doesn’t look great, we have an

infracost output --format slack-message

command, see this screenshot for how it looks. But I suppose you’d have to find a way to disable job from posting that comment to slack (it’s probably not possible?) and add this command to the gitlab CI yaml instead.

Unfortunately, it seems like there is no much room for configuration for these Slack notifications as CLI posts a regular comment 😞 https://docs.gitlab.com/ee/user/project/integrations/slack.html