https://cloudposse.com logo
Join Slack
Powered by
Hey guys, I have a question about `ci.comments` is...
# atmos
m
Hey guys, I have a question about 
ci.comments
is there a ENV to disable this? https://atmos.tools/cli/configuration/ci/comments I like it and want it for most of my CI/CD workflows but I'm trying to do a custom drift detection workflow where I will not like this to be trigger but I don't see a way to disable this using an ENV like 
ATMOS_COMMENTS_ENABLED=FALSE
e
Yeah, that makes total sense. I don't know if we have it right now. Can you create the GitHub issue and we'll come up with something quickly?
m
I'm trying the ai-prompt to see how that works but I guess is in progress? hahaha idk how this works https://github.com/cloudposse/atmos/issues/2299?reload=1
e
It's been assigned 😉
Please try 
--use-version=2300
and let me know if that works for you
m
Oh nice I will try it in a bit 😛
@Erik Osterman (Cloud Posse) Sorry for the delay I'm creating a new workflow to test this bc the workflow that I was going to use had a new issue hehehe
btw aparently the plan summary template is not finding 
.Additions
maybe this is a new but but I'm testing it to see if it's maybe a missconfiguration on my side or it's new bug bc according to the docs this should exist on plan. Here is the error for reference:
Copy code
WARN CI summary failed
  error=
  │ template evaluation failed: template evaluation failed: template: ci-summary:6:6: executing "ci-summary" at <.Additions>: can't evaluate field Additions in type *terraform.TerraformTemplateContext
  │ (1) forced error mark
  │   | "template evaluation failed"
  │   | errors/*errors.errorString::
  │ Wraps: (2) template=plan
  │ Wraps: (3) Failed to render template
  │ Wraps: (4) template evaluation failed: template evaluation failed: template: ci-summary:6:6: executing "ci-summary" at <.Additions>: can't evaluate field Additions in type *terraform.TerraformTemplateContext
  │     └─ Wraps: (5) forced error mark
e
what version?
Are you using the built-in template or a custom one?
m
Version 
1.214.0
a custom one, this is why it might be my fault but it looks like I need to fix this bc I can't test the 
ATMOS_CI_COMMENTS_ENABLED
ENV since it complains about this either way (for this test I did use 
--use-version=2300
on a simple plan)
is there a validation cmd for templates?
e
Not yet
Can you create a feature request for that?
m
@Erik Osterman (Cloud Posse) Here it's: https://github.com/cloudposse/atmos/issues/2321 PS: Sorry for the delay
Open in Slack
PreviousNext
Powered by