#atlantis (2021-09)
Discuss the Atlantis (<http://runatlantis.io | runatlantis.io>) |
**Archive: ** https://archive.sweetops.com/atlantis/
2021-09-14
![tomv avatar](https://secure.gravatar.com/avatar/44a7bbeb9f6711e508a0141d8b365470.jpg?s=72&d=https%3A%2F%2Fa.slack-edge.com%2Fdf10d%2Fimg%2Favatars%2Fava_0019-72.png)
any chance there is an atlantis chart maintainer in here? i have a small pull request that would save me from not having to maintain my own fork up the upstream chart
The requirements of my base container force me to use a different uid, this patch helps me use the upstream chart while still using a custom Atlantis container.
![jose.amengual avatar](https://secure.gravatar.com/avatar/32f267b819eac9e0ea6a8324b53064a0.jpg?s=72&d=https%3A%2F%2Fa.slack-edge.com%2Fdf10d%2Fimg%2Favatars%2Fava_0024-72.png)
done
The requirements of my base container force me to use a different uid, this patch helps me use the upstream chart while still using a custom Atlantis container.
![tomv avatar](https://secure.gravatar.com/avatar/44a7bbeb9f6711e508a0141d8b365470.jpg?s=72&d=https%3A%2F%2Fa.slack-edge.com%2Fdf10d%2Fimg%2Favatars%2Fava_0019-72.png)
very much appreciated @jose.amengual
![tomv avatar](https://secure.gravatar.com/avatar/44a7bbeb9f6711e508a0141d8b365470.jpg?s=72&d=https%3A%2F%2Fa.slack-edge.com%2Fdf10d%2Fimg%2Favatars%2Fava_0019-72.png)
thanks!!
![jose.amengual avatar](https://secure.gravatar.com/avatar/32f267b819eac9e0ea6a8324b53064a0.jpg?s=72&d=https%3A%2F%2Fa.slack-edge.com%2Fdf10d%2Fimg%2Favatars%2Fava_0024-72.png)
np
![Erik Osterman (Cloud Posse) avatar](https://secure.gravatar.com/avatar/88c480d4f73b813904e00a5695a454cb.jpg?s=72&d=https%3A%2F%2Fa.slack-edge.com%2Fdf10d%2Fimg%2Favatars%2Fava_0023-72.png)
![Erik Osterman (Cloud Posse) avatar](https://secure.gravatar.com/avatar/88c480d4f73b813904e00a5695a454cb.jpg?s=72&d=https%3A%2F%2Fa.slack-edge.com%2Fdf10d%2Fimg%2Favatars%2Fava_0023-72.png)
(in my screenshot, i should have only indented two, but you get the drift. the problem is that as written, the yaml map starts on the wrong line)
![jose.amengual avatar](https://secure.gravatar.com/avatar/32f267b819eac9e0ea6a8324b53064a0.jpg?s=72&d=https%3A%2F%2Fa.slack-edge.com%2Fdf10d%2Fimg%2Favatars%2Fava_0024-72.png)
ohhhhh yes that will screw the yaml….good catch @Erik Osterman (Cloud Posse)
![jose.amengual avatar](https://secure.gravatar.com/avatar/32f267b819eac9e0ea6a8324b53064a0.jpg?s=72&d=https%3A%2F%2Fa.slack-edge.com%2Fdf10d%2Fimg%2Favatars%2Fava_0024-72.png)
@tomv can you address that?
![tomv avatar](https://secure.gravatar.com/avatar/44a7bbeb9f6711e508a0141d8b365470.jpg?s=72&d=https%3A%2F%2Fa.slack-edge.com%2Fdf10d%2Fimg%2Favatars%2Fava_0019-72.png)
yep!
![tomv avatar](https://secure.gravatar.com/avatar/44a7bbeb9f6711e508a0141d8b365470.jpg?s=72&d=https%3A%2F%2Fa.slack-edge.com%2Fdf10d%2Fimg%2Favatars%2Fava_0019-72.png)
nindent
is a helper that adds a new line prior to the indentation
![tomv avatar](https://secure.gravatar.com/avatar/44a7bbeb9f6711e508a0141d8b365470.jpg?s=72&d=https%3A%2F%2Fa.slack-edge.com%2Fdf10d%2Fimg%2Favatars%2Fava_0019-72.png)
rendered template from main:
![jose.amengual avatar](https://secure.gravatar.com/avatar/32f267b819eac9e0ea6a8324b53064a0.jpg?s=72&d=https%3A%2F%2Fa.slack-edge.com%2Fdf10d%2Fimg%2Favatars%2Fava_0024-72.png)
ahh so it will do newline first I see ok
![jose.amengual avatar](https://secure.gravatar.com/avatar/32f267b819eac9e0ea6a8324b53064a0.jpg?s=72&d=https%3A%2F%2Fa.slack-edge.com%2Fdf10d%2Fimg%2Favatars%2Fava_0024-72.png)
ok, so then we should be good
![tomv avatar](https://secure.gravatar.com/avatar/44a7bbeb9f6711e508a0141d8b365470.jpg?s=72&d=https%3A%2F%2Fa.slack-edge.com%2Fdf10d%2Fimg%2Favatars%2Fava_0019-72.png)
yep yep, have been using that branch for a little bit now
![jose.amengual avatar](https://secure.gravatar.com/avatar/32f267b819eac9e0ea6a8324b53064a0.jpg?s=72&d=https%3A%2F%2Fa.slack-edge.com%2Fdf10d%2Fimg%2Favatars%2Fava_0024-72.png)
were you able to use the new release?
![jose.amengual avatar](https://secure.gravatar.com/avatar/32f267b819eac9e0ea6a8324b53064a0.jpg?s=72&d=https%3A%2F%2Fa.slack-edge.com%2Fdf10d%2Fimg%2Favatars%2Fava_0024-72.png)
I was having issues with the helm release pipeline
![tomv avatar](https://secure.gravatar.com/avatar/44a7bbeb9f6711e508a0141d8b365470.jpg?s=72&d=https%3A%2F%2Fa.slack-edge.com%2Fdf10d%2Fimg%2Favatars%2Fava_0019-72.png)
i was not, i just assumed a manual tag had to be created and i didn’t want to bother you again
![tomv avatar](https://secure.gravatar.com/avatar/44a7bbeb9f6711e508a0141d8b365470.jpg?s=72&d=https%3A%2F%2Fa.slack-edge.com%2Fdf10d%2Fimg%2Favatars%2Fava_0019-72.png)
ah, okay, i need to update chart.yaml
![tomv avatar](https://secure.gravatar.com/avatar/44a7bbeb9f6711e508a0141d8b365470.jpg?s=72&d=https%3A%2F%2Fa.slack-edge.com%2Fdf10d%2Fimg%2Favatars%2Fava_0019-72.png)
Atlantis Helm Chart. Contribute to runatlantis/helm-charts development by creating an account on GitHub.
![tomv avatar](https://secure.gravatar.com/avatar/44a7bbeb9f6711e508a0141d8b365470.jpg?s=72&d=https%3A%2F%2Fa.slack-edge.com%2Fdf10d%2Fimg%2Favatars%2Fava_0019-72.png)
^ Also updated the README.md to specify use case for statefulSet.securityContext
![jose.amengual avatar](https://secure.gravatar.com/avatar/32f267b819eac9e0ea6a8324b53064a0.jpg?s=72&d=https%3A%2F%2Fa.slack-edge.com%2Fdf10d%2Fimg%2Favatars%2Fava_0024-72.png)
ahhh that is why it failed, the version update
![jose.amengual avatar](https://secure.gravatar.com/avatar/32f267b819eac9e0ea6a8324b53064a0.jpg?s=72&d=https%3A%2F%2Fa.slack-edge.com%2Fdf10d%2Fimg%2Favatars%2Fava_0024-72.png)
ok
![jose.amengual avatar](https://secure.gravatar.com/avatar/32f267b819eac9e0ea6a8324b53064a0.jpg?s=72&d=https%3A%2F%2Fa.slack-edge.com%2Fdf10d%2Fimg%2Favatars%2Fava_0024-72.png)
I will merge that
![jose.amengual avatar](https://secure.gravatar.com/avatar/32f267b819eac9e0ea6a8324b53064a0.jpg?s=72&d=https%3A%2F%2Fa.slack-edge.com%2Fdf10d%2Fimg%2Favatars%2Fava_0024-72.png)
now is failing about something else
![Erik Osterman (Cloud Posse) avatar](https://secure.gravatar.com/avatar/88c480d4f73b813904e00a5695a454cb.jpg?s=72&d=https%3A%2F%2Fa.slack-edge.com%2Fdf10d%2Fimg%2Favatars%2Fava_0023-72.png)
nindent! Thanks
![jose.amengual avatar](https://secure.gravatar.com/avatar/32f267b819eac9e0ea6a8324b53064a0.jpg?s=72&d=https%3A%2F%2Fa.slack-edge.com%2Fdf10d%2Fimg%2Favatars%2Fava_0024-72.png)
release is ready
![tomv avatar](https://secure.gravatar.com/avatar/44a7bbeb9f6711e508a0141d8b365470.jpg?s=72&d=https%3A%2F%2Fa.slack-edge.com%2Fdf10d%2Fimg%2Favatars%2Fava_0019-72.png)
hmmm, unfortunately it looks like it didn’t actually release https://github.com/runatlantis/helm-charts/runs/3613111288
![tomv avatar](https://secure.gravatar.com/avatar/44a7bbeb9f6711e508a0141d8b365470.jpg?s=72&d=https%3A%2F%2Fa.slack-edge.com%2Fdf10d%2Fimg%2Favatars%2Fava_0019-72.png)
maaaybe related? https://github.com/helm/chart-releaser-action/issues/13
When running this action, it's checking for charts that have changed since the same commit. For instance the release workflow was triggered by commit da27374 and is checking for changes since t…
![jose.amengual avatar](https://secure.gravatar.com/avatar/32f267b819eac9e0ea6a8324b53064a0.jpg?s=72&d=https%3A%2F%2Fa.slack-edge.com%2Fdf10d%2Fimg%2Favatars%2Fava_0024-72.png)
it did release
![jose.amengual avatar](https://secure.gravatar.com/avatar/32f267b819eac9e0ea6a8324b53064a0.jpg?s=72&d=https%3A%2F%2Fa.slack-edge.com%2Fdf10d%2Fimg%2Favatars%2Fava_0024-72.png)
![tomv avatar](https://secure.gravatar.com/avatar/44a7bbeb9f6711e508a0141d8b365470.jpg?s=72&d=https%3A%2F%2Fa.slack-edge.com%2Fdf10d%2Fimg%2Favatars%2Fava_0019-72.png)
it released the artifact but didn’t update the repository manifest: https://runatlantis.github.io/helm-charts/index.yaml
![jose.amengual avatar](https://secure.gravatar.com/avatar/32f267b819eac9e0ea6a8324b53064a0.jpg?s=72&d=https%3A%2F%2Fa.slack-edge.com%2Fdf10d%2Fimg%2Favatars%2Fava_0024-72.png)
we released 3.14.2 which have your changes
![tomv avatar](https://secure.gravatar.com/avatar/44a7bbeb9f6711e508a0141d8b365470.jpg?s=72&d=https%3A%2F%2Fa.slack-edge.com%2Fdf10d%2Fimg%2Favatars%2Fava_0019-72.png)
![tomv avatar](https://secure.gravatar.com/avatar/44a7bbeb9f6711e508a0141d8b365470.jpg?s=72&d=https%3A%2F%2Fa.slack-edge.com%2Fdf10d%2Fimg%2Favatars%2Fava_0019-72.png)
What was the issue exactly? Just a transient error?
![jose.amengual avatar](https://secure.gravatar.com/avatar/32f267b819eac9e0ea6a8324b53064a0.jpg?s=72&d=https%3A%2F%2Fa.slack-edge.com%2Fdf10d%2Fimg%2Favatars%2Fava_0024-72.png)
the github action released 3.14.1 but did not updated the index.yaml because on an earlier failure
![tomv avatar](https://secure.gravatar.com/avatar/44a7bbeb9f6711e508a0141d8b365470.jpg?s=72&d=https%3A%2F%2Fa.slack-edge.com%2Fdf10d%2Fimg%2Favatars%2Fava_0019-72.png)
ah, cool.
2021-09-15
2021-09-16
![Jurgen avatar](https://secure.gravatar.com/avatar/915965c8a95b0d97f7d201423fdff980.jpg?s=72&d=https%3A%2F%2Fa.slack-edge.com%2Fdf10d%2Fimg%2Favatars%2Fava_0011-72.png)
with custom workflows; can I get the status of the plan or apply (success or fail) and still run something after?
![jose.amengual avatar](https://secure.gravatar.com/avatar/32f267b819eac9e0ea6a8324b53064a0.jpg?s=72&d=https%3A%2F%2Fa.slack-edge.com%2Fdf10d%2Fimg%2Favatars%2Fava_0024-72.png)
there is always a lock
![jose.amengual avatar](https://secure.gravatar.com/avatar/32f267b819eac9e0ea6a8324b53064a0.jpg?s=72&d=https%3A%2F%2Fa.slack-edge.com%2Fdf10d%2Fimg%2Favatars%2Fava_0024-72.png)
so as long as is not locked you can run something
![jose.amengual avatar](https://secure.gravatar.com/avatar/32f267b819eac9e0ea6a8324b53064a0.jpg?s=72&d=https%3A%2F%2Fa.slack-edge.com%2Fdf10d%2Fimg%2Favatars%2Fava_0024-72.png)
lock is per repo
![Jurgen avatar](https://secure.gravatar.com/avatar/915965c8a95b0d97f7d201423fdff980.jpg?s=72&d=https%3A%2F%2Fa.slack-edge.com%2Fdf10d%2Fimg%2Favatars%2Fava_0011-72.png)
yeah, I am not talking aboutg that
![jose.amengual avatar](https://secure.gravatar.com/avatar/32f267b819eac9e0ea6a8324b53064a0.jpg?s=72&d=https%3A%2F%2Fa.slack-edge.com%2Fdf10d%2Fimg%2Favatars%2Fava_0024-72.png)
no per folder in a repo
![Jurgen avatar](https://secure.gravatar.com/avatar/915965c8a95b0d97f7d201423fdff980.jpg?s=72&d=https%3A%2F%2Fa.slack-edge.com%2Fdf10d%2Fimg%2Favatars%2Fava_0011-72.png)
so maybe I reword the question.
So; my plan or apply has run… I want to know its status code. exit 0; exit 1; or plan success or plan fail.
catch it and run differnt commands
![jose.amengual avatar](https://secure.gravatar.com/avatar/32f267b819eac9e0ea6a8324b53064a0.jpg?s=72&d=https%3A%2F%2Fa.slack-edge.com%2Fdf10d%2Fimg%2Favatars%2Fava_0024-72.png)
mmmm no any error is catch before the next command is run
![Jurgen avatar](https://secure.gravatar.com/avatar/915965c8a95b0d97f7d201423fdff980.jpg?s=72&d=https%3A%2F%2Fa.slack-edge.com%2Fdf10d%2Fimg%2Favatars%2Fava_0011-72.png)
in bash I would be like
terraform plan
status=$?
if [ $status = 0 ]; then
stuff
else
other stuff
fi
![jose.amengual avatar](https://secure.gravatar.com/avatar/32f267b819eac9e0ea6a8324b53064a0.jpg?s=72&d=https%3A%2F%2Fa.slack-edge.com%2Fdf10d%2Fimg%2Favatars%2Fava_0024-72.png)
you can runa custom command with a bash script to do that
![Jurgen avatar](https://secure.gravatar.com/avatar/915965c8a95b0d97f7d201423fdff980.jpg?s=72&d=https%3A%2F%2Fa.slack-edge.com%2Fdf10d%2Fimg%2Favatars%2Fava_0011-72.png)
https://www.runatlantis.io/docs/custom-workflows.html#custom-init-plan-apply-commands
are those the defaults?
Atlantis: Terraform Pull Request Automation
![jose.amengual avatar](https://secure.gravatar.com/avatar/32f267b819eac9e0ea6a8324b53064a0.jpg?s=72&d=https%3A%2F%2Fa.slack-edge.com%2Fdf10d%2Fimg%2Favatars%2Fava_0024-72.png)
I think they are
![Jurgen avatar](https://secure.gravatar.com/avatar/915965c8a95b0d97f7d201423fdff980.jpg?s=72&d=https%3A%2F%2Fa.slack-edge.com%2Fdf10d%2Fimg%2Favatars%2Fava_0011-72.png)
cool, thank you
2021-09-17
![jose.amengual avatar](https://secure.gravatar.com/avatar/32f267b819eac9e0ea6a8324b53064a0.jpg?s=72&d=https%3A%2F%2Fa.slack-edge.com%2Fdf10d%2Fimg%2Favatars%2Fava_0024-72.png)
Credits to Dan Williams : https://tech.loveholidays.com/enforcing-best-practice-on-self-serve-infrastructure-with-terraform-atlantis-and-policy-as-code-911f4f8c3e00
![attachment image](https://miro.medium.com/max/1200/0*96l9ueS9UhMBETT2.png)
Here at loveholidays we are heavily dependant on Terraform. All of our Google Cloud infrastructure is managed using Terraform, along with a…
2021-09-24
![SlackBot avatar](https://slack.global.ssl.fastly.net/66f9/img/slackbot_32.png)
This message was deleted.
2021-09-27
![Carlos Tovar avatar](https://secure.gravatar.com/avatar/5868d73984661a019d50bfc7b354ad13.jpg?s=72&d=https%3A%2F%2Fa.slack-edge.com%2Fdf10d%2Fimg%2Favatars%2Fava_0017-72.png)
Hi everyone - we are going through the process of upgrading to terraform fro 0.13 to 1.0 and ran into the consideration of what to do with the new terraform dependency lock files. I understand they should be committed, but for new terraform stacks, they are created by Atlantis, which is not going to commit it. How are people handling this consideration?
![joshmyers avatar](https://avatars.slack-edge.com/2018-11-20/483958217281_8117d6f6c62807ce9912_72.jpg)
Generate manually and commit. Atlantis will use.
![Carlos Tovar avatar](https://secure.gravatar.com/avatar/5868d73984661a019d50bfc7b354ad13.jpg?s=72&d=https%3A%2F%2Fa.slack-edge.com%2Fdf10d%2Fimg%2Favatars%2Fava_0017-72.png)
Thanks @joshmyers!
![Steve Wade (swade1987) avatar](https://avatars.slack-edge.com/2022-12-08/4499411930625_2768e5fdceec550e6669_72.jpg)
I know @loren recommends git ignoring them
![joshmyers avatar](https://avatars.slack-edge.com/2018-11-20/483958217281_8117d6f6c62807ce9912_72.jpg)
Why?
![Erik Osterman (Cloud Posse) avatar](https://secure.gravatar.com/avatar/88c480d4f73b813904e00a5695a454cb.jpg?s=72&d=https%3A%2F%2Fa.slack-edge.com%2Fdf10d%2Fimg%2Favatars%2Fava_0023-72.png)
If you do decide to use them, make sure to lock for all architectures you’re using. E.g.
terraform providers lock \
-platform=linux_arm64 \
-platform=linux_amd64 \
-platform=darwin_amd64 \
-platform=windows_amd64
![Erik Osterman (Cloud Posse) avatar](https://secure.gravatar.com/avatar/88c480d4f73b813904e00a5695a454cb.jpg?s=72&d=https%3A%2F%2Fa.slack-edge.com%2Fdf10d%2Fimg%2Favatars%2Fava_0023-72.png)
so developers and atlantis are in sync