https://www.runatlantis.io/ logo
Join Slack
Powered by
This message was deleted.
# atlantis-community
s
This message was deleted.
l
Are you using auto-merge?
https://www.runatlantis.io/docs/server-configuration.html#automerge can make it so, once all plans are applied, the atlantis merges the MR
d
yes, using automerge. But as i mentioned this functionality would be required to merge MR's where 
there are no
module changes. Meaning nothing to be planned/applied by atlantis.
l
in my experience, I often use 
atlantis apply
on no-op MRs to "merge" them for me
If there are no plans at all you can always run 
atlantis plan
and get (hopefully!) a no-op plan
d
peculiar how does it work for you? as no 
apply
or 
plan
does anything really :{ perhaps it is because its custom workflows for terragrunt? but the logs say "there is nothing to plan/apply"
l
I usually run a manual plan at that point
since autoplan won't have been triggered
it's not something that comes up too frequently for me so it's an OK workaround
d
i did right after that, damn wanted to include it in, but didnt
atlantis plan
yielded just 2 eyes again and thats it ;D
l
oh hm, maybe it didn't know which workspace to plan, hmm
d
maybe, you use vanilla tf?
l
no I use tg workflow
d
using terragrunt + terragrunt-atlantis-config ;D
then prolly you too
could you help me out pulling your atlantis logs when you re able to perform a merge like that?
l
You could try running a particular plan: 
atlantis plan -d . -w default
or something
d
(its ok if its too much to ask)
You could try running a particular plan: 
atlantis plan -d . -w default
or something
that does make sense, will give it a go thx
l
yeah I just realized I'm not sure what 
atlantis plan
does when it doesn't know which workspace to plan 🤔
that said, it shouldn't just say 
:eyes:
then nothing
d
logs are "nothing to plan"
-d should do the trick
l
ah yeah I guess that makes sense
d
same as when destroying ;D
another pain innit?
l
I would have expected a comment saying "nothing to plan"
d
maybe terragrunt-atlantis-config at play
l
can you paste the log line here?
Just the one that says "nothing to plan", I'd like to poke at the code to see if it makes sense to comment that back
This of course doesn't solve your problem, just thinking about how troubleshooting might have been easier 🙂
d
cant find the log, wip on mr recreate
Copy code
atlantis {"level":"info","ts":"2023-11-06T14:49:30.062Z","caller":"events/project_command_builder.go:435","msg":"0 projects are to be planned based on their when_modified config","json":{"repo":"terraform","pull":"628"}}

atlantis {"level":"info","ts":"2023-11-06T14:49:30.062Z","caller":"events/plan_command_runner.go:97","msg":"determined there was no project to run plan in","json":{"repo":"terraform","pull":"628"}}
on autoplan, on 
atlantis plan
, and just the latter log on 
atlantis plan -d .
cause must atlantis.yaml generated by tg-atlantis-config. checking if a give a real dir
so definitely can merge this now
well its a way, yah, not as clean as something like 
atlantis merge
could be, but still
and now thinking about it, someone could 
atlantis merge
a PR with real module changes 😁 means building gates.. painful
l
yeah that was my thought in my own environment; downside is there's this extra step of a plan, but at least I know there's nothing being snuck in 🙂
d
fair. offtop, how do you do destroys? same way?
l
I haven't needed to do destroys I don't think
d
plan -- -destroy
apply --auto-merge-disabled
then wipe the module thats the last what we've come to in a bigger setups where 2+ teams touch tf code = can't avoid the need to destroy
with tg another big pain is if you plan 2 modules, but one depends on the state output of another. can do a tg plan with mocks, but due to nature of planfile and etc in atlantis workflows - then you can only apply that mocked plan
havent seen this discussed on atlantis issues, so now that i'm live chatting with someone, you'll have to pardon my zeal
l
haha no worries
Open in Slack
PreviousNext
Powered by