Description
Community Note
- Please vote on this issue by adding a 👍 reaction to the original issue to help the community and maintainers prioritize this request. Searching for pre-existing feature requests helps us consolidate datapoints for identical requirements into a single place, thank you!
- Please do not leave "+1" or other comments that do not add relevant new information or questions, they generate extra noise for issue followers and do not help prioritize the request.
- If you are interested in working on this issue or have submitted a pull request, please leave a comment.
- I'd be willing to implement this feature (contributing guide)
Describe the user story
Describe the solution you'd like
The auto discover (discovery / autodiscovery / autodiscover) feature of Atlantis is relied on by many Atlantis users since it is the default. Most users do not know the magic that is used to calculate the discovered projects to get auto planning to work and so it should be documented.
This will allow greater understanding and future improvements to the feature.
Here are some gems for the documentation writer
buildAllCommandsByCfg
atlantis/server/events/project_command_builder.go
Lines 375 to 421 in 885a4e1
Calls FindModuleProjects
atlantis/server/events/modules.go
Lines 121 to 123 in 00cad3a
Calls findModuleDependants
atlantis/server/events/modules.go
Lines 125 to 161 in 885a4e1
Calls getProjectDirFromFs
atlantis/server/events/project_finder.go
Lines 283 to 344 in 885a4e1