building template via UI does not support setting terraform vars #7410
Comments
|
#7153 is different, which aims to prevent redirection (stay in editor) after someone presses "Publish template." The issue with this is that variables without a default say "missing parameter" |
This comment was marked as outdated.
This comment was marked as outdated.
|
If a managed variable doesn't have a default, I'm pretty sure the template creation fails inside the template editor. When using the CLI, you can provide variables at "runtime". This mismatch doesn't feels right. As a user, I wish the CLI/UI would prompt me for missing variable values. I'm also not sure how this works with rich parameters without a default, however I think this case is less important since it seems like almost all scenarios require a rich parameter has a default value. |
|
Maybe add a temporary variable to use when building the template (mock_value = "random"). So it will mock the a valid variable on the build. Even tho its just a workaround, it would be awesome a prompt window with the inputs to fill-out the user requested variables. |
|
We should add inputs and persist the value for the session of the template editor. |
|
@BrunoQuaresma as we disabled legacy parameters, and tweaked the Template Editor, would mind checking if this issue still valid? |
|
It is already done! 
|
when terraform variables are declared in a template, the CLI will prompt the user to set these vars when running
coder templates create | push.this is not the case when editing and building a template in the UI. it will error out and require setting defaults or hard-coding the variables in the code itself rather than prompt the user as done in the CLI.
related #7408
The text was updated successfully, but these errors were encountered: