#atlantis (2021-09)
| Discuss the Atlantis (<http://runatlantis.io | runatlantis.io>) |
**Archive: ** https://archive.sweetops.com/atlantis/
2021-09-14
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
very much appreciated @jose.amengual
thanks!!
np
(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)
ohhhhh yes that will screw the yaml….good catch @Erik Osterman (Cloud Posse)
@tomv can you address that?
yep!
nindent is a helper that adds a new line prior to the indentation
rendered template from main:
ahh so it will do newline first I see ok
ok, so then we should be good
yep yep, have been using that branch for a little bit now
were you able to use the new release?
I was having issues with the helm release pipeline
i was not, i just assumed a manual tag had to be created and i didn’t want to bother you again
ah, okay, i need to update chart.yaml
^ Also updated the README.md to specify use case for statefulSet.securityContext
ahhh that is why it failed, the version update
ok
I will merge that
now is failing about something else
nindent! Thanks
release is ready
hmmm, unfortunately it looks like it didn’t actually release https://github.com/runatlantis/helm-charts/runs/3613111288
it did release
it released the artifact but didn’t update the repository manifest: https://runatlantis.github.io/helm-charts/index.yaml
we released 3.14.2 which have your changes
What was the issue exactly? Just a transient error?
the github action released 3.14.1 but did not updated the index.yaml because on an earlier failure
ah, cool.
2021-09-15
2021-09-16
with custom workflows; can I get the status of the plan or apply (success or fail) and still run something after?
there is always a lock
so as long as is not locked you can run something
lock is per repo
yeah, I am not talking aboutg that
no per folder in a repo
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
mmmm no any error is catch before the next command is run
in bash I would be like
terraform plan
status=$?
if [ $status = 0 ]; then
stuff
else
other stuff
fi
you can runa custom command with a bash script to do that
https://www.runatlantis.io/docs/custom-workflows.html#custom-init-plan-apply-commands
are those the defaults?
I think they are
cool, thank you
2021-09-17
2021-09-24
This message was deleted.
2021-09-27
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?
Generate manually and commit. Atlantis will use.
Thanks @joshmyers!
I know @loren recommends git ignoring them
Why?
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
so developers and atlantis are in sync