Supporting Variable Sets

[mbevc1]

Use-cases

New feature released: https://www.hashicorp.com/blog/terraform-cloud-variable-sets-beta-now-available

Attempted Solutions

/

Proposal

It seems it's already part of API: https://www.terraform.io/docs/cloud/api/variable-sets.html
I recognize it's still in beta, but it would be nice have a resource in TFE for configuring it.

[madtank]

Thanks for opening this feature request. What I would need is ability to add variable sets to a workspace. Creating and updating the variable sets would be nice option too.

[elocke]

Thanks for submitting this, variable sets solve a problem very elegantly for us but cannot be used easily without the provider supporting them.

[dkirrane]

Any ETA for this?

[madtank]

Any ETA for this?

I was told April 2022 timeframe.

[rorychatterton]

A couple of items that would be useful for customers like myself when implementing this provider:

Seperate Set from Assignment objects

Can you please ensure that we have separate objects to handle the creation of the variable set, away from the assignment of that variable set. For example:

Not this:

resource "tfe_variable_set" "my_set" {
   tfe_workspaces = [...]
}

But rather this:

resource "tfe_variable_set" "my_set" {}
resource "tfe_variable_set_assignment" "my_set_assignment_ws_1" {
    variable_set = ""
    tfe_workspaces = ""
}

We would like this to be able to decouple the creation of global variable sets, from the assignment to workspaces. This particular pain point exists with the policy workspace, and it would be great if we could avoid it here!

Handle Complex Terraform Objects

The current terraform variable class doesn't handle complex objects. If you want to output a complex object into a terraform managed variable (such as a map of objects), you must convert that object into a string (we normally use json encode).

This limits the usefulness of the variable provider as you are not able to do type validation on the consuming workspace side.

I have raised an issue here for resolution in the context of standard variables. In essence, handle:

resource "tfe_variable_set" "my_set" {
   variable {
     key = "value1"
     value = { subkey1 = "...", subkey2 = "..."}
  }
}

[Satak]

This would be very useful 🤞

[ryanisnan]

Plus one on this feature!

[morremeyer]

That's what a thumbs up reaction is for. In the future, please don't spam people with notifications just to express your support of an idea.

[mbevc1]

Nice one, we have Variable Sets supports merged in and available with 0.30.0!

[jacobtaunton]

I'm getting an error adding a workspace to a varset.

resource "tfe_variable_set" "this" {
name = "var.varset"
organization = var.organization
workspaces = tfe_workspace.this.id
}

on ../modules/workspaces/main.tf line 46, in resource "tfe_variable_set" "this":
│ 46: workspaces = tfe_workspace.this.id
│
│ An argument named "workspaces" is not expected here.

[morremeyer]

It's `wonkspace_ids`, the docs are wrong here. The documentation bug is being fixed, there's already a PR for it.

[madtank]

It's wonkspace_ids, the docs are wrong here. The documentation bug is being fixed, there's already a PR for it.

That’s sort of funny :)
Thanks!