scalr_workspace Data Source¶

This data source is used to retrieve details of a single workspace by name.

Example Usage¶

data "scalr_workspace" "example" {
  name           = "my-workspace-name"
  environment_id = "env-xxxxxxxxx"
}

The following arguments are supported:

name - (Required) Name of the workspace.
environment_id - (Required) ID of the environment, in the format env-<RANDOM STRING>.

All arguments plus:

id - The workspace’s ID, in the format ws-<RANDOM STRING>.
auto_apply - Boolean indicates if terrafrom apply will be automatically run when terraform plan ends without error.
operations - Boolean indicates if the workspace is being used for remote execution.
terraform_version - The version of Terraform used for this workspace.
working_directory - A relative path that Terraform will execute within.
module_version_id - The identifier of a module version in the format modver-<RANDOM STRING>.
vcs_provider_id - The identifier of a VCS provider in the format vcs-<RANDOM STRING>.
vcs_repo - If workspace is linked to VCS repository this block shows the details, otherwise {}
created_by - Details of the user that created the workspace.
has_resources - The presence of active terraform resources in the current state version.
hooks - List of the workspace’s custom hooks.

The hooks block supports:
- pre_plan - Script or action configured to call before plan phase
- post_plan - Script or action configured to call after plan phase
- pre_apply - Script or action configured to call before apply phase
- post_apply - Script or action configured to call after apply phase

The vcs_repo block contains:

identifier - * The reference to the VCS repository in the format :org/:repo, this refers to the organization and repository in your VCS provider.
path - Path within the repo, if any.
dry_runs_enabled - Boolean indicates the VCS driven dry runs should run when pull request to configuration versions branch created.

The created_by block contains: