* each of those variables support the value `auto`: in that case, the template will use the dynamic [`$environment_slug` value](#deployment-context-variables) as workspace name,
* if the specified workspace doesn't exist, the template will create it,
* HTTP backend doesn't support Workspaces. [See supported backends here](https://developer.hashicorp.com/terraform/language/state/workspaces#backends-supporting-multiple-workspaces).
* corollary as Gitlab http backend is on by default workspace selection is explicitly bypassed
* corollary as GitLab http backend is on by default workspace selection is explicitly bypassed
unless `gitlab-backend-disabled` / `TF_GITLAB_BACKEND_DISABLED` is set to `true`.
If kept enabled and if any of the `TF_WORKSPACE` variable is set the template will warn about it.
* if using another (non-Gitlab) http backend nothing will prevent from trying to use workspaces, in