- Notifications
You must be signed in to change notification settings - Fork1k
feat: enable Terraform template-wide variables by default#8334
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 ourterms of service andprivacy statement. We’ll occasionally send you account related emails.
Already on GitHub?Sign in to your account
Uh oh!
There was an error while loading.Please reload this page.
Changes fromall commits
File filter
Filter by extension
Conversations
Uh oh!
There was an error while loading.Please reload this page.
Jump to
Uh oh!
There was an error while loading.Please reload this page.
Diff view
Diff view
There are no files selected for viewing
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -248,12 +248,14 @@ data "coder_parameter" "cpu" { | ||
As a template improvement, the template author can consider making some of the new `coder_parameter` resources `mutable`. | ||
## Terraform template-wide variables | ||
> ⚠️ Flag `feature_use_managed_variables` is available until v0.25.0 (Jul 2023) release. After this release, template-wide Terraform variables will be enabled by default. | ||
Member There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others.Learn more. Should this mention the coder provider version as well? (Edit: On second thought, maybe not.) There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others.Learn more. In theory, terraform-provider-coder still accepts the | ||
As parameters are intended to be used only for workspace customization purposes, Terraform variables can be freely managed by the template author to build templates. Workspace users are not able to modify | ||
template variables. | ||
The template author can enable Terraform template-wide variables mode by specifying the following flag: | ||
```hcl | ||
provider "coder" { | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others.Learn more. Shouldn't the Coder provider be bumped to 0.10.0? In all of the example templates? There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others.Learn more. It is a valid point, but I'd rather do this in a separate PR as more examples will be affected. |
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -12,7 +12,6 @@ terraform { | ||
} | ||
provider "coder" { | ||
} | ||
variable "ecs-cluster" { | ||
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -12,7 +12,6 @@ terraform { | ||
} | ||
provider "coder" { | ||
} | ||
variable "step1_do_project_id" { | ||
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -38,7 +38,6 @@ variable "use_kubeconfig" { | ||
} | ||
provider "coder" { | ||
} | ||
variable "namespace" { | ||
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -19,7 +19,6 @@ provider "fly" { | ||
} | ||
provider "coder" { | ||
} | ||
resource "fly_app" "workspace" { | ||
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -12,7 +12,6 @@ terraform { | ||
} | ||
provider "coder" { | ||
} | ||
variable "project_id" { | ||
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -12,7 +12,6 @@ terraform { | ||
} | ||
provider "coder" { | ||
} | ||
variable "project_id" { | ||
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -12,7 +12,6 @@ terraform { | ||
} | ||
provider "coder" { | ||
} | ||
variable "project_id" { | ||
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -12,7 +12,6 @@ terraform { | ||
} | ||
provider "coder" { | ||
} | ||
variable "use_kubeconfig" { | ||