-
Notifications
You must be signed in to change notification settings - Fork 1.1k
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
feat: support atlantis.yaml without defined projects #2300
feat: support atlantis.yaml without defined projects #2300
Conversation
@csainty please fix conflicts and see above comment |
@csainty I resolved the conflicts here to merge from main. Please see the test failures. |
Fixed up the test, sorry it took me a while to get back to this one, the first comments came through while I was on vacation, so it fell out of the inbox. |
@csainty Thank you for resolving! We are planning the v0.21.0 release at the moment so this PR will have to wait after that to avoid too many changes. @jamengual regarding this change, I saw you added the |
I was trying to understand the need for the feature and if it was not going to break anything in the current atlantis.yaml parsing process |
You can't, to my knowledge, turn on parallel processing without listing all your projects in the config file. |
Regarding a more general refactor, my inclination is to abstract the notion of the configuration file so that the calling code just asks for the config and then the parser layer either returns the file or a generated default. I haven't attempted it yet, but I assume it will have tendrils that reach to a lot of code, which is where the diff-vs-code comment came from. I can find some time to give it a shot though and see just how far it reaches out. |
@csainty the new version has been released and I'm sorry to say there are 2 small conflicts. Could you resolve those one last time and we can merge? Thank you again |
f5ea697
to
5b6a04b
Compare
@nitrocode done. |
* Support atlantis.yaml without defined projects * Update server/events/project_command_builder.go * Update server/events/project_command_builder.go * Correct test of no modified projects * Flip if statement * Remove duplicate check on hasRepoCfg Co-authored-by: nitrocode <[email protected]>
I'd like to propose supporting
atlantis.yaml
config without having to specify the projects section. Enabling, for example, to setparallel_plan
while still having atlantis determine the project list.I totally understand if this doesn't fit with your own ideas, so there are no hard feelings if you disagree and close.
The code gets a bit fiddly, and I am not Go expert, but this looks like to relevant section to change, there just may be side-effects I am unaware of.
Relates to #2708