-
Notifications
You must be signed in to change notification settings - Fork 2
Change on tf_vars should also trigger a new template version #97
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. Weβll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
Just saw that the vars in coder are defined on the template level, not the project level. What happens if I push two versions with different vars via coderd... which values for the vars will be promoted in the template? Or is this only on the coder UI? |
I was also confused by this, but the Terraform variables shown on template settings are populated from the active template version. However, they are applied template-wide. If you created a new version using Regardless, we very much have a bug in the provider, as it needs to be pushing a new template version when |
Okay, thank you for the confirmation. Out of curiosity: if I switch the active template version to an older one, will the vars get overwritten by the vars of the old template? Edit: Just tried it out, this is exactly what happens. If I promote an older version, the vars get reset to the vars of that version |
Currently, a change in the tf_vars property does not trigger a recreation but a modification of the template.
As the tf_vars effectively change the content of the template, it should trigger a new version.
As an example, it would be possible to change the name of a parameter via tf_var.
A more drastic example to show what would be possible is to base the entire coder parameters on a tf_var:
template.tf
in the template:
If I change the content of the parameters var via the coderd_template in this scenario, the whole template would change.
The text was updated successfully, but these errors were encountered: