| copyright | lastupdated | keywords | subcollection | ||
|---|---|---|---|---|---|
|
2025-01-17 |
schematics workspaces, workspaces, schematics |
schematics |
{{site.data.keyword.attribute-definition-list}}
{: #sc-workspaces}
{{site.data.keyword.bpshort}} workspaces delivers Terraform as a service capabilities to automate the provisioning and configuration management of your {{site.data.keyword.cloud_notm}} resources, and rapidly build, duplicate, and scale complex, multitiered cloud environments.
Terraform{: external} is an open source project that allows you to specify your cloud infrastructure resources and services as code. It applies the concept of Infrastructure as Code (IaC), using code to manage and provision infrastructure (networks, virtual machines, load-balancers, clusters, services and connection topology) in a descriptive model instead of manual processes. {: shortdesc}
With Terraform, configuration files define your infrastructure, which also makes it easier to edit, share, and reuse configurations. By codifying your infrastructure, you provision the same environment every time avoiding undocumented, ad hoc configuration changes.
The blog Infrastructure as Code: Chef, Ansible, Puppet, or Terraform?{: external} provides an overview of several of the most popular open-source IaC tools and summarizes their capabilities and relative strengths.
{: #sch-wks-overview}
{{site.data.keyword.bplong_notm}} is a multi-tenant service delivering Terraform as a service. {{site.data.keyword.bpshort}} provides a shared environment, where each user can securely run Terraform configs to deploy services and resources on {{site.data.keyword.cloud}}.
{: caption="Deploying infrastructure and services with workspaces" caption-side="bottom"}
Using your supplied Terraform template (config), {{site.data.keyword.bpshort}} executes the Terraform CLI engine to provision the resources defined in the config. {{site.data.keyword.bpshort}} provides a secure container environment to execute the Terraform engine, using the {{site.data.keyword.cloud_notm}} Terraform provider to provision and manage resources using the {{site.data.keyword.cloud_notm}} service APIs.
{: #sc-wks-features}
{{site.data.keyword.bplong_notm}} provides built in remote-state management for Terraform. Terraform state files are automatically preserved between runs and are accessible by {{site.data.keyword.bpshort}} commands and operations. {{site.data.keyword.bpshort}} remote-state management enables team work and workspace shared operations, with built in state locking preventing concurrent operations against the same state file.
Workspaces is designed for teams. Terraform templates can be stored in a GitHub, GitLab, or Bitbucket repositories to ensure source control and enable collaboration, review, and auditing in your organization.
Workspaces support drift detection, detecting when the configuration of your deployed infrastructure differs from the wanted state that is defined in your template configuration. Drift can occur for many reasons. The most frequent cause changes that are applied manually outside of Terraform automation.
{: #sc-wks-nextsteps}
So far you have learned about {{site.data.keyword.bpshort}} workspaces. The following are some next steps to explore. {: shortdesc}
- Getting started use case to understand how to use workspaces to deploy and manage your Infrastructure as Code (IaC), in the cloud, environments.
- Sample Terraform templates to provide you how to create well-structured, and reusable Terraform templates.
- See Creating workspaces to dig into how to create workspace using the Terraform templates.