-
Notifications
You must be signed in to change notification settings - Fork 93
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
.json files support ? #243
Comments
Support for custom files in general, not just json, would be great. Technically you can do this with locals {
module_source = "../../../modules/atlantis"
dependency1_source = "${get_terragrunt_dir()}/../dependency1"
dependency2_source = "${get_terragrunt_dir()}/../dependency2"
extra_atlantis_dependencies = [
"${local.module_source}/*.json",
"${local.module_source}/*.yaml",
"${local.module_source}/*.etc",
]
} Another hacky workaround would be to name your <customfiletype> files .tf.<customfiletype>, like .tf.json or .tf.yaml. This is simple but you run the risk of people forgetting to do this. But it would be a lot easier and cleaner to just pass in a flag |
Actually, that doesn't work because then terraform thinks those are actual terraform files and you get syntax errors >_< |
Another possibility is to go the opposite route and just filter out markdown files. It would be much more inclusive of different files types. It's highly unlikely that someone wants to dynamically read in markdown files into terraform code. https://www.runatlantis.io/docs/repo-level-atlantis-yaml.html#configuring-planning https://docs.docker.com/build/building/context/#negating-matches |
is the file whose name ends with
.json
supported by this tool to generateatlantis.yaml
?context: we are submitting a
file_name.json
to Atlantis, befor plan and apply runs, we are running a pre-workflow hookterragrunt-atlantis-config_1.14.2_linux_amd64 generate --output atlantis.yaml --parallel=false --autoplan --automerge --ignore-dependency-blocks=true
which is generatingatlantis.yaml
file but forfile_name.json
it didn't made any entry inatlantis.yaml
and because of that no plan ran for that file.captured server logs when we push such file
The text was updated successfully, but these errors were encountered: