-
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
If repo_config_file is not found, plan should just skip #3339
Comments
Hello @nicarnold-toast, thanks for reaching out. That is correct, if no repoConfigFile is found Atlantis will try to autodetect Terraform modules that are modified in the PR. atlantis/server/events/project_command_builder.go Lines 390 to 432 in f4fa313
You are asking for a way to disable this behavior? |
Hey @GenPage . Thanks for getting back to me. I think your suggestion around disabling this might be the better option in this case (as it appears this is already an established pattern). Would you like me to follow up with a PR in this case? Many thanks, |
Hello Nic, yes PRs are welcome |
A pr for this has already been created and is awaiting review. Please comment and add feedback when time permits |
Community Note
Overview of the Issue
When specifying a
repo_config_file
override, I would expect if the file does not exist, that the plan would just be skipped over.This does not happen. Atlantis attempts to plan the project despite there being no repo config. It seems to use the default config (atlantis.yaml)
Reproduction Steps
Setup webhook to an atlantis server.
Push to repo without the
atlantis-nonproduction.yaml
Logs
Logs
looks like it originates from here: https://github.com/runatlantis/atlantis/blob/main/server/events/project_command_builder.go#L392
Environment details
e0ea4a5f3fa6
<- docker shaAtlantis server-side config file:
Repo
atlantis.yaml
file:N/A
Additional Context
The text was updated successfully, but these errors were encountered: