Closed subrasub closed 1 year ago
Hey @subrasub - thanks for this! But these descriptions are set in the resource object, the markdown is then generated from them using make doc
, could you update? thanks!
Also, reading your comment, I'm not sure this is clear? Are you just saying the environment names are case sensitive and need to exactly match how the environment is configured?
i.e. Environment name Production
can't have env vars under production
?
Just tested this out and it works for non title-cased envs too, i.e. staging
Add a note to title-case environment names. If we don't title-casing the environment names, it can throw a 500 error when we run
terraform apply
. For eg: if we are setting the environment variables for the Production env, the environment name should also beProduction
.Related - https://github.com/GtheSheep/terraform-provider-dbt-cloud/issues/108#issue-1586440179