Stop Plan/Apply, Global Unlock, and Comment to File

[biker2o]

I have three requests

1. Please provide a way to stop/cancel actively running plans and applies.

2. Please provide a way to unlock outside of a pull request AND/OR allow unlocking of, for example, pull request 49 plans inside of pull request 50.

3. I use Atlantis with Bitbucket Cloud and when the Atlantis comment are too long, it breaks them up into separate comments. However these comments cannot be read straight down from top to bottom - you have to jump around. Please have Atlantis comment in a readable straight top to bottom manner AND/OR allow Atlantis to write to a file with a readable plan.

[nishkrishnan]

1. We have an issue open for this: Ability to cancel a plan/apply using atlantis cancel #187
2. We have the ability to unlock through the UI.
3. Can you clarify this one? At least with Github, Atlantis just breaks the plans into multiple comments that occur right after one another. Curious why this wouldn't be the case for another VCS like bitbucket.

[biker2o]

@nishkrishnan For unlocking in the UI, there is no "Unlock All" and no select feature. There are times I have 100+ plans and would have to individually click and delete each plan one by one

As for the comments, let's say it is supposed to look like this

A
B
C
D
E
F
G
H
I

When Atlantis comments inside a bitbucket PR, it comes out like this (with each set of three being it's own individual comment).

G
H
I

D
E
F

A
B
C

[biker2o]

Hi @nishkrishnan , any update on this?

[ghost]

@biker2o as a quick workaround for closing multiple plans, you can close the offending PR temporarily then reopen it after you've completed plans in another PR.

It's not as good as what you're suggesting though, +1 for your points #1 and #2 (I don't use Bitbucket so no idea about #3).

[brandon-fryslie]

Can someone re-open this? This gets really annoying when people are keeping their branches up to date with head and each one triggers a new plan, possibly locking other PRs touching the same modules. We have a lot of people making changes. We might just have to disable auto-plan all together

[jamengual]

I will prefer to leave this closed, this work as designed and we do not have time to implement these changes.
If you are willing to create a PR and tests and docs to add a new feature, then create a new issue and link this one.

You can now disable locking globally, or autoplan globally, or per project so you can tailor your projects in whatever way you want.

I personally always thought autoplan was a pain so I always disable it and created atlantis.yaml files..

[brandon-fryslie]

I personally always thought autoplan was a pain so I always disable it and created atlantis.yaml files

We have roughly 100 modules across multiple repos. Turning off autoplan is a huge pain. But maybe we're just busier than most teams. Disabling Atlantis locking globally fixed the immediate problem where only one PR could plan at at time. It would be nice if Atlantis allowed disabling locking for plan but leaving it enabled for apply, but now we're just relying on Terraform locking for that.

We do create atlantis.yaml files, but it's generated by a python script and around 7000 lines long...

[jamengual]

using workspaces eliminates that problem too

…

On Sat, Sept 9, 2023, 12:53 a.m. Brandon Fryslie ***@***.***> wrote: I personally always thought autoplan was a pain so I always disable it and created atlantis.yaml files We have roughly 100 modules across multiple repos. Turning off autoplan is a huge pain. But maybe we're just busier than most teams. Disabling Atlantis locking globally fixed the immediate problem where only one PR could plan at at time. It would be nice if Atlantis allowed disabling locking for plan but leaving it enabled for apply, but now we're just relying on Terraform locking for that. We do create atlantis.yaml files, but it's generated by a python script and around 7000 lines long... — Reply to this email directly, view it on GitHub <#1491 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAQ3ERAK7QOVHO3EL6IB26DXZQN6DANCNFSM42T3NAIQ> . You are receiving this because you commented.Message ID: ***@***.***>