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
Yes I understand why it can't be done. Terraform HCL does not provide any field to be used for pretty ne. We can't use description as it's longer.
May be a data in coder provider can be used to create a title for every variable.
We have a plan to replace variable with a coder_parameter data source. The scheme is TBD but it would allow us to have friendly names, validate on the frontend, and mark specific variables as immutable. related: #802
Legacy variables would be supported, but wouldn't show up as pretty in the dashboard
There are other ways we could do it without that (e.g. mapping common terms in the backend, replacing underscores with spaces), but I think we should wait until we have more controls with coder_parameter :).
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.
Activity
BrunoQuaresma commentedon Sep 15, 2022
@matifali what a pretty name should be?
matifali commentedon Sep 15, 2022
For example
var.ramcan be Total RAMvar.cpucan be CPU Coresvar.docker_imageDocker ImageBrunoQuaresma commentedon Sep 15, 2022
Since these var names are dynamic and came from terraform I don't see how we could use better names 🤔 Any ideas?
matifali commentedon Sep 15, 2022
Yes I understand why it can't be done. Terraform HCL does not provide any field to be used for pretty ne. We can't use description as it's longer.
May be a data in coder provider can be used to create a title for every variable.
BrunoQuaresma commentedon Sep 16, 2022
cc.: @bpmct
bpmct commentedon Sep 16, 2022
We have a plan to replace
variablewith acoder_parameterdata source. The scheme is TBD but it would allow us to have friendly names, validate on the frontend, and mark specific variables as immutable. related: #802For example,
Legacy
variableswould be supported, but wouldn't show up as pretty in the dashboardThere are other ways we could do it without that (e.g. mapping common terms in the backend, replacing underscores with spaces), but I think we should wait until we have more controls with
coder_parameter:).bpmct commentedon Sep 16, 2022
We should keep this issue open until there is a way to do that, though :)
github-actions commentedon Nov 24, 2022
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.
BrunoQuaresma commentedon Nov 24, 2022
This is done in the latest version