Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Unable to use slack notification #247

Open
yury-kustov-sb opened this issue Sep 7, 2022 · 1 comment
Open

Unable to use slack notification #247

yury-kustov-sb opened this issue Sep 7, 2022 · 1 comment

Comments

@yury-kustov-sb
Copy link

I use terragrunt-atlantis-config as pre_workflow_hooks in atlantis so it generates a new atlantis.yaml every run.
To use native slack notifications webhook block have to be added to atlantis.yaml(https://www.runatlantis.io/docs/using-slack-hooks.html#configuring-atlantis)
I did't found any options to add custom block to autogenerated config, is there any hope to do that or concerns why option like "custom block" did't added already?

thank you!

@gmaghera
Copy link
Contributor

gmaghera commented Sep 15, 2022

The docs are a bit confusing on this. You can add this to your repo configuration YAML file instead (config.yaml by default, I think). If you deploy via Helm, you can follow the documentation example I added a few weeks ago:

image

We use terragrunt-atlantis-config on the client side (repo is too large to run it fully on all plans), and there is a way to add custom blocks, if you wrap their script with a shell script of your own. You can use something like yq (python-yq, not the other one). In our case, it's something that always gets appended, so we just use cat.

(This issue is a better fit for the Atlantis repo, too, IMO)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants