You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The doc you referenced is for the Crunchy Bridge API and are referring to how someone might set an environment variable to be compatible with the curl examples used to demonstrate direct use of the API. Those examples don't really influence the function of the Terraform provider. (Some of the Terraform-specific documentation has been duplicated in the Crunchy Bridge documentation for visibility, but the Terraform registry contains the complete documentation for the provider)
As far as I'm aware, using TF_VAR_* approach isn't a workaround, it is the built-in mechanism in Terraform for configuring via the environment. It saves unnecessary duplication of custom-implementing environment variable reads on a per-provider basis and also avoids having to establish precedence rules resolving conflicts between the built-in TF_VAR mechanism and a provider custom one.
So that I can understand your use case better - what benefit are you hoping to achieve with a parallel and seemingly redundant implementation of environment variable reads?
It would like to set
application_secret
provider config via an environment variable. The docs already make use ofCRUNCHY_API_KEY
in the examples.Terraform variables and
TF_VAR_*
environment variables can be used as a workaround.The text was updated successfully, but these errors were encountered: