TF_CLI_CONFIG_FILE env var does not seem to be honoured when populating credentials

[aaklilu]

Hi @dflook,

What's the best way to provide a .terraformrc file for provider installation while utilising the TERRAFORM_CLOUD_TOKENS? I'm using jfrog terraform provider repository as a provider mirror which requires the mirror configuration and access token.

I've tried providing TF_CLI_CONFIG_FILE step env var but it does not seem to be augmented with the credentials provided via TERRAFORM_CLOUD_TOKENS env var.

Looking at how the write_credentials function works here, it appears to be copying an existing .terraformrc file from $HOME...How do I supply this?

Thanks

[dflook]

It wasn't intended for a .terraformrc file to be supplied, even though it takes care to use what is there and undo any changes it makes to it. $HOME is shared by all container based action steps, so it could be placed there from within a previous container based action. There isn't an easy way to get this directory from the host runner, but it was /home/runner/work/_temp/_github_home on GitHub hosted runners the last time I checked.

I think the best way for you to provide the provider_installation would be to add it using a script in the TERRAFORM_PRE_RUN environment variable, e.g.

env:
  TERRAFORM_PRE_RUN: |
    cat >> $HOME/.terraformrc <<EOF

    provider_installation {
        direct {
            exclude = ["registry.terraform.io/*/*"]
        }
        network_mirror {
            url = "<YOUR_JFROG_DOMAIN>/artifactory/api/terraform/<REPOSITORY_KEY>/providers/"
        }
    }
    EOF

(I haven't tested this)
The TERRAFORM_CLOUD_TOKENS would already be in the file by the time the script runs.

[aaklilu]

I'll try that...thanks @dflook!