custom_environment_variables with ATLANTIS_REPO_CONFIG_JSON about terraform-aws-atlantis

[lkysow]

Hmm, have you tried restarting the container? It seems really weird that it's not showing up.

[ivanmartos]

Yes I tried restarting and nothing changed. Maybe one more thing to add - I saw in CloudWatch logs this entry

WARNING: Flag --allow-repo-config has been deprecated.
Create a --repo-config file with the following config instead:
---
repos:
- id: /.*/
allowed_overrides: [apply_requirements, workflow]
allow_custom_workflows: true
or use --repo-config-json='
{
    "repos": [
        {
            "id": "/.*/",
            "allowed_overrides": [
                "apply_requirements",
                "workflow"
            ],
            "allow_custom_workflows": true
        }
    ]
}
'

Don't know whether it is related to this or not

[lkysow]

It looks like either the --allow-repo-config flag or ATLANTIS_ALLOW_REPO_CONFIG=true environment variables are being set. Based on the config you listed this seems impossible. Can you verify the fargate config matches what you set in your terraform?

[nitrocode]

Interesting. I had the same issue.

I did have allow_repo_config = "true" set in the terraform-aws-modules/terraform-aws-atlantis module. Once I disabled that option, the workflow started to work as expected.

I didn't realize that allow_repo_config option was deprecated, was insecure, prevented the server configuration, and was unnecessary since directory specific configurations can still work on the repo level, just the atlantis server keys are no longer accessible when it's disabled.

@lkysow is this documented ?

[lkysow]

There's these docs: https://www.runatlantis.io/docs/server-side-repo-config.html

[bryantbiggs]

hey @ivanmartos / @nitrocode - is this still an issue or were you able to resolve?

[bryantbiggs]

closing for now, please feel free to reach back out if this is still an issue

[github-actions]

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.