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

atlantis apply should apply all unapplied plans #169

Closed
chaseconey opened this issue Jul 5, 2018 · 7 comments
Closed

atlantis apply should apply all unapplied plans #169

chaseconey opened this issue Jul 5, 2018 · 7 comments

Comments

@chaseconey
Copy link
Contributor

Hello there,

Just upgraded to Atlantis 0.4.0 and the autoplan feature is working nicely, but it seems that when going to apply the planned feature after approval it isn't tracking like it did in 0.3.8.

Steps to error:

  • Make change in terraform project
  • Make pull request
  • Autoplan runs properly on the sub-directory and output looks good
  • Reviewer adds approval
  • Run command atlantis apply and receive error:
Ran Apply in dir: . workspace: default
Apply Error

no plan found at path "." and workspace "default"–did you run plan?
@lkysow
Copy link
Member

lkysow commented Jul 5, 2018

@chaseconey right, I think maybe it should be changed back to atlantis apply apply'ing all outstanding plans and atlantis apply -d/-w applying a specific plan. Let me look into that and until then you'll have to use the -d flag.

@chaseconey
Copy link
Contributor Author

Yeah that is how I ended up getting around it. Let me know if you need any other info!

Thanks

lkysow added a commit that referenced this issue Jul 5, 2018
@lkysow lkysow changed the title Autoplan + Apply Not Working atlantis apply should apply all unapplied plans Jul 11, 2018
@rmldsky
Copy link

rmldsky commented Jul 18, 2018

@lkysow additionally it seems running manually atlantis plan has the same problem:

Ran Plan in dir: . workspace: default
Plan Error

I mean it expects user to provide -d, even though automated plan ran as expected in dirs/subdirs where changes have been made. It is confusing just because all documentation and guides mention just running atlantis plan and atlantis apply without any flags, which I believe was a case before 0.4.0 release.

Thanks for all the hard work! :)

@lkysow
Copy link
Member

lkysow commented Jul 18, 2018

Thanks Dawid, yes they should both be changed to plan all/apply all

@bentterp
Copy link

I believe the default should be that approving a pull request should only lead to those changes being carried out. I.e. only that specific plan should be applied

Imagine if approving a pull request would merge all code from all open pull requests into the master branch. I don't see people liking that feature being rolled out on GH.

Of course, the default could be configurable.

All in all, it looks like Atlantis could be a really good, free alternative to TF Enterprise. I'm impressed!

@oba11
Copy link

oba11 commented Jul 23, 2018

@bentterp thought of thesame thing as well. It would be nice to have autoapply once a PR is approved.
It works brilliantly for me, running it in fargate with custom modules. Thank you @lkysow 🥇

@lkysow
Copy link
Member

lkysow commented Aug 10, 2018

Closed by #216 and available in the latest release: v0.4.5.

@lkysow lkysow closed this as completed Aug 10, 2018
jamengual pushed a commit that referenced this issue Nov 23, 2022
* remove unused constants

* remove unused functions in global_cfg.go

* Adding default workflows for platform mode

* refactor global_cfg.go

* Adding tests

* Merging server config to project

* moving config from events/yaml to core/config

* move PR and deployment workflows into their own maps

* use correct method
meringu pushed a commit to meringu/atlantis that referenced this issue May 29, 2023
Update CONTRIBUTING.md with steps to start local development
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

5 participants