Scalr workspace variables

Sync an environment with one Scalr workspace's shell variables.

Connection

What	This provider
Vendor	Scalr
Key	`scalr-variables`
Availability	`available`. You can connect it today.
Credential we hold	`scalr-token`
Values read back	yes
Activation	`on-next-deploy`

Direction	What it does
`import`	We read names and values out of the store into your environment.
`export`	We write names and values from your environment into the store.

on-next-deploy. A new value waits there and arrives with your next deploy.

Direction	Policies you can pick
`import`	`skip_existing`, `new_version`, `fail`
`export`	`create_only`, `overwrite`, `overwrite_and_prune`

How syncs work says what each one does.

Paste a credential from the vendor. We seal it and never show it again.

Field	Label	Kind	Required	What it is
`token`	API token	secret; we mask it here and seal it	yes	A service account token. At the account scope, open Security, then IAM, then Service accounts, pick or create a service account, and create a token for it. Give it an access policy on the workspace with a role that has the variable:* permission.

You set these when you connect. Every mapping on the connection shares them.

Field	Label	Kind	Required	Advanced	What it is
`account`	Account	text	yes	no	The part of your Scalr address before .scalr.io.

You answer these once per environment you map.

Field	Label	Kind	Required	Advanced	What it is
`workspaceId`	Workspace ID	text	yes	no	From the workspace URL. We sync its shell variables and never touch the ones it inherits from the environment or account. Pruning deletes every shell variable of this workspace that this environment lacks, including ones this sync did not write.
`sensitive`	Mark written variables sensitive	yes or no	yes	yes	Scalr never shows a sensitive value again, including to import, and a sensitive variable cannot be made plain. We never turn it off on a variable that has it. Starts at `true`.

We probe for these when we verify the connection.

Permission	Directions	Blocking	Without it
`Role with the variable:* permission`	every direction	yes	We cannot list the workspace's variables, or add, change or remove one on export.