2 Commits (179e108cd1b1541b53bc355efcd2b9cd7ac277ff)

Author	SHA1	Message	Date
Brandon Croft	1f01ba4dbc	fix(run variables): support all variable types (map, list, bool, number, null, string) ... All run variables remain encoded as strings in the API but will now be expressed as an HCL value to be evaluated correctly by the remote terraform. Previously, only strings were supported. Examples: string: `"quoted literal"` (strings must be quoted) map: `{ foo = "bar" }` list: `["foo", "bar"]` bool: `true` null: `null` number: `0.0001` This requires the API to anticipate that all run variables will be HCL values	4 years ago
Omar Ismail	dd856f8a1b	Add run variables to cloud plan operations from non-file sources ... Run variables allow the run API to accept input variables not found in the configuration slug (the file-based ones plus workspace vars)	5 years ago