-
-
Notifications
You must be signed in to change notification settings - Fork 355
Allow providing ATLANTIS_REPO_CONFIG_JSON as a YAML file #204
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
Comments
Agree, PR is welcome :) |
Great! I just wanted to open discussion for the different methods to do this. Documenting it would be easy but an input variable would probably be better. If no one has an opinion, then I'd like to put in a PR for an input |
I think it will be fine if we ask users to pass it like this: atlantis_repo_config_yaml_file = jsonencode(yamldecode(file("${path.module}/server-atlantis.yaml"))) |
Fixed in #205 |
I'm going to lock this issue because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues. If you have found a problem that seems similar to this, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further. |
Is your request related to a new offering from AWS?
No
Is your request related to a problem? Please describe.
The problem is that people think the only way to provide this information is by using a json file which is untrue. Something like this can be used.
server-atlantis.yaml
main.tf
Describe the solution you'd like.
We could provide a couple inputs
atlantis_repo_config_json
atlantis_repo_config_yaml_file
Describe alternatives you've considered.
We could simply document the
jsonencode(yamldecode(file(
methodAdditional context
#116
The text was updated successfully, but these errors were encountered: