You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The `environment:set-variables` and `pipeline:set-variables` commands allow for variables to be passed both as flags to the command and as a JSON array provided as standard input or as a file. The objects in this array are expected to have a `name`, `value`, and `type` keys following the same syntax as the Cloud Manager API. Deleting a variable can be done by passing an empty `value`. For example, given a file named `variables.json` that contains this:
721
+
722
+
```
723
+
[
724
+
{
725
+
"name" : "MY_VARIABLE",
726
+
"value" : "something",
727
+
"type" : "string"
728
+
},
729
+
{
730
+
"name" : "MY_SECRET_VARIABLE",
731
+
"value" : "shhhh",
732
+
"type" : "secretString"
733
+
}
734
+
]
735
+
```
736
+
737
+
This can be passed to the `pipeline:set-variables` command using a shell command of
description: 'if set, read variables from a JSON array provided as standard input; variables set through --variable or --secret flag will take precedence'
162
+
}),
163
+
jsonFile: flags.string({
164
+
description: 'if set, read variables from a JSON array provided as a file; variables set through --variable or --secret flag will take precedence',
0 commit comments