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.yaml "default" config for all projects / dirs #490

Closed
zytek opened this issue Feb 22, 2019 · 3 comments
Closed

atlantis.yaml "default" config for all projects / dirs #490

zytek opened this issue Feb 22, 2019 · 3 comments
Labels
feature New functionality/enhancement

Comments

@zytek
Copy link

zytek commented Feb 22, 2019

I had a basic atlantis setup working fine, with multiple directories inside a repo - that were correctly "discovered" and planned/applied by atlantis on a per-directory basis.

I wanted to run force terraform fmt check using atlantis.yaml: https://gist.github.com/zytek/1d82ec0d7fdff09110765c451fd54129

Unfortunately such setup breaks directory/project discovery and runs plan only in . dir. Is there a way to overcome that other than specifying ALL dirs/projects in atlantis.yaml? That would be a lot of copy-pasted setup. :/

@zytek
Copy link
Author

zytek commented Feb 22, 2019

Seems related to #244 - so this is just another use case for default keyword.

@lkysow
Copy link
Member

lkysow commented Feb 22, 2019

Hi Jakub, right now there is no other way unfortunately. I think you need #244 so I'm going to close this as a duplicate.

@lkysow lkysow closed this as completed Feb 22, 2019
@lkysow
Copy link
Member

lkysow commented Feb 22, 2019

Perhaps the Terraform GitHub actions might be useful to you as a workaround (if you're on GitHub): https://github.com/hashicorp/terraform-github-actions

@lkysow lkysow added the feature New functionality/enhancement label Apr 9, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
feature New functionality/enhancement
Projects
None yet
Development

No branches or pull requests

2 participants