This topic describes how to create and manage projects in HCP Terraform and Terraform Enterprise. A project is a folder containing one or more workspaces.
You must have the following permissions to manage projects:
To delete tags on a project, you must be member of a team with the Admin permission group enabled for the project.
To create tags for a project, you must be member of a team with the Write permission group enabled for the project.
To view your organization's projects:
HCP Terraform returns a new project page displaying all the project information.
On this General settings page, you can update the project name, project description, and delete the project. On the Team access page, you can modify team access to the project.
Note: Ephemeral workspaces, which automatically destroy infrastructure, are available in HCP Terraform Plus and Premium editions. Refer to HCP Terraform pricing for details.
You can configure HCP Terraform to automatically destroy each workspace's infrastructure in a project after a period of inactivity. A workspace is inactive if the workspace's state has not changed within your designated time period.
If you configure a project to auto-destroy its infrastructure when inactive, any run that updates Terraform state further delays the scheduled auto-destroy time by the length of your designated timeframe.
Warning
The user interface does not prompt you to approve automated destroy plans. We recommend only using this setting for development environments.
To schedule an auto-destroy run after a period of workspace inactivity:
You can configure an individual workspace's auto-destroy settings to override this default configuration. Refer to automatically destroy workspaces for more information.
You can only delete projects that do not contain stacks or workspaces.
To delete an empty project:
HCP Terraform returns to the Projects view with the deleted project removed from the list.
You can define tags stored as key-value pairs to help you organize your projects and track resource consumption. Workspaces created in the project automatically inherit the tags, but workspace administrators with appropriate permissions can attach new key-value pairs to their workspaces to override inherited tags. Refer to Create workspace tags for additional information about using tags in workspaces.
The following rules apply to tag keys and values:
Navigate to the organization settings and choose the execution mode. Enabling the Remote execution mode instructs HCP Terraform or Terraform Enterprise to perform Terraform runs on its own disposable virtual machines. This provides a consistent and reliable run environment and enables advanced features such as Sentinel policy enforcement, cost estimation, notifications, and version control integration.
To disable remote execution for a project, enable the Local execution. This mode lets you perform Terraform runs locally with the CLI-driven run workflow.
You can let HCP Terraform or Terrafomr Enterprise to communicate with isolated, private, or on-premises infrastructure, consider using HCP Terraform agents. By deploying a lightweight agent, you can establish a simple connection between your environment and HCP Terraform or Terraform Enterprise.
Changing your project's execution mode after a run has already been planned causes the run to error when it is applied.
To minimize the number of runs that error when changing your project's execution mode, complete the following steps:
RetroSearch is an open source project built by @garambo | Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4