If you enter a string in this field and press enter, only workspaces whose names contain that string will be shown. Workspace search bar: The search field at the far right of the filter bar lets you filter workspaces by name. You can sort the list by workspace name by alphabetical order, or by the latest change time for the workspace.
Health filter - The health filter lists workspaces based on the results of the last health assessment: Drifted, Health error, or Check failed.Ĭolumn sorting: For any columns marked with two arrows, you can click the arrows to change the sort order for the column. When you choose a status filter, the list will only include workspaces whose current runs match the selected statuses. Status filter - The status filter shows a list of all possible statuses that apply to workspaces.
Choosing one or more will show only workspaces tagged with all of the chosen tags. Tag filter: The tag filter shows a list of tags added to all workspaces, limited to the first 1,000 tags alphabetically. There are five quick filter buttons that collect the most commonly used groups of statuses: Needs Attention, Errored, Running, On Hold, and Applied. Run Status filter buttons: These filters display workspaces with the selected run status. If your organization has many projects, click the search icon next to Projects to find a project. Clicking on a project will filter the workspaces list to show only the workspaces in the selected project. Project filter: Click the left chevron icon next to Workspaces to open the project drawer. If your organization contains many workspaces, you can use the filter tools at the top of the list to find the workspaces you are interested in. The project drawer lists any projects the user has access to. Terraform Cloud displays the workspaces the current user account has permission to read runs for. Note: The explorer for workspace visibility surfaces a wider range of valuable information from across your workspaces. Refer to Workspaces in the Terraform Language documentation for more details. The Terraform CLI does not require you to create CLI workspaces. Terraform CLI workspaces are associated with a specific working directory and isolate multiple state files in the same working directory, letting you manage multiple groups of resources with a single configuration. You cannot manage resources in Terraform Cloud without creating at least one workspace. You can grant individual users and user groups permissions for one or more workspaces that dictate whether they can manage variables, perform runs, etc. They are also a major component of role-based access in Terraform Cloud. They represent all of the collections of infrastructure in an organization. Terraform CLI Workspacesīoth Terraform Cloud and Terraform CLI have features called workspaces, but they function differently. Refer to Terraform Runs and Remote Operations for more details. Terraform Runsįor workspaces with remote operations enabled (the default), Terraform Cloud performs Terraform runs on its own disposable virtual machines, using that workspace's configuration, variables, and state. This includes both managed resources and data sources. The top of each workspace shows a resource count, which reflects the number of resources recorded in the workspace’s state file. Refer to Viewing and Managing Runs for more details. Run history: When Terraform Cloud manages a workspace's Terraform runs, it retains a record of all run activity, including summaries, logs, a reference to the changes that caused the run, and user comments. Refer to Terraform State in Terraform Cloud for more details. Although only the current state is necessary for managing resources, the state history can be useful for tracking changes over time or recovering from problems. State versions: Each workspace retains backups of its previous state files. In addition to the basic Terraform content, Terraform Cloud keeps some additional data for each workspace:
0 kommentar(er)
