Is it related to #5980? I have a feeling that it overlaps a bit.

Yeah, I think it's related but wanted a separate issue for workspace-scoped env vars. (I was assuming this would be a parameter type like bool, string: but key_value) where the other one was Terraform variables.

Ok, I see :) I assumed that every variable would have a type and format too, even if they are strict Terraform variables, which could be a string type without format restrictions.

This issue is becoming stale. In order to keep the tracker readable and actionable, I'm going close to this issue in 7 days if there isn't more activity.

@mtojek Using the terraform variable, we could easily set secrets at template push time. I understand this is now deprecated, and that there is no alternative. Is this similar to this ticket or is there another tracking one?

I understand this is now deprecated, and that there is no alternative.

Incorrect. You can still use Terraform variables, but with feature_use_managed_variables provider flag.

If you set sensitive = true, you can use the variable to pass secrets.

@mtojek I have tried and tried, the coder cli does not take into account the TF_VAR_X anymore with managed variables. Neither was I able to get a similar behaviour using coder_parameter data source. Is there a doc on what is expected to work with env var?

You can try to use values.yml file:

region: us-east-1
secret_field: magic
cpu: 1

then:

coder templates push my-awesome-template -d my-template-directory --variables-file values.yml

@mtojek we use Lade to inject secret as temporary environment variables. Mounting a file is more cumbersome, therefore my comment about the ability to load secrets via env vars.

@mtojek I saw that coder 0.24.x was released with all legacy parameters removed. Do you have an idea when loading parameter through env var will be back on the roadmap?

I have tried and tried, the coder cli does not take into account the TF_VAR_X anymore with managed variables. Neither was I able to get a similar behaviour using coder_parameter data source.
we use Lade to inject secret as temporary environment variables. Mounting a file is more cumbersome, therefore my comment about the ability to load secrets via env vars.

I can confirm that it is not on the roadmap now, and we don't plan to work on it in the nearest future. I understand that using a config file is unfortunate for your case.

EDIT:

If you want to prepare a community contribution, we will gladly review it!

@mtojek I have given a try, and it seems there is still different than previous way to load env vars. The values.yml I am using is following your guidance. Yet during the template push, I get:

Looks like the variables may not be present during that step of the build? Also reading the doc again, it seems that template user may see those values (or afaik). Is that correct?

Looks like the variables may not be present during that step of the build? Also reading the doc again, it seems that template user may see those values (or afaik). Is that correct?

Yes, unless you mark them as sensitive.

BTW It would be easier to guide you if you share your template and the command you're calling.

@mtojek and @bpmct, I think this issue is no longer relevant.