Introduction

Terraform maturity stages

While working with our customers, we have identified common patterns of maturity, allowing us to categorize customers into three main stages: Adopt, Standardize, and Scale. Each of the maturity stages is covered in a separate HVD document and assumes that the previous maturity stage is successfully implemented.

Adopt: These customers have recently partnered with HashiCorp and are investing substantially in adopting IaC for their enterprise. These customers lay the groundwork for growth by embracing fundamental use cases (as listed in the table above) facilitated by the HCP Terraform platform.

Standardize: These customers have completed the Adopt use cases and are now prioritizing the availability of the Platform as a shared service for the entire organization. At this stage of maturity, the platform team focuses on establishing guardrails by implementing policy-as-code and utilizing modules from the private registry and completing the development of an automated onboarding process for internal customers.

Scale: Once the platform is available to the wider organization and workloads are provisioned using an efficient, unified workflow, the platform team will need to address issues such as cost management, optimization, and other related use cases. These measures will ensure efficient scaling of operations for the organization over time.

Prerequisites

Review HashiCorp's cloud operating model which enables your organization to unlock the fastest path to value in a modern multi-cloud datacenter:

• Cloud Operating Model

If you are using Terraform Enterprise, this guide assumes that you have reviewed and implemented the following HVDs:

• Terraform: Solution Design Guide (Self-Managed)

HVD document structure

This document covers the "Adopt" phase of operating Terraform on the maturity scale and includes the following:

Objectives

You are implementing HCP Terraform/Enterprise to achieve your company's business and functional objectives. Here, we list what we expect the goals you should realize after implementing the recommendations detailed in this guide.

Business objectives

1. Reduce time to market: This guide will assist you in establishing a robust standard workflow for provisioning, configuring, and managing the lifecycle of hybrid/multi cloud infrastructure. When implemented effectively, developers can provision infrastructure more efficiently, reducing the time it takes for your organization to introduce new products and features to the market.
2. Mitigate risk: By securing Terraform state, protecting cloud credentials, and implementing RBAC (role-based access control), you will significantly reduce the risk associated with your infrastructure.
3. Consistent compliance: Through policy-as-code, organizations will achieve compliant infrastructure, automate audit, address asset lineage concerns, manage against cost expectations, and respond proactively to regulatory change.
4. Improve skills and retention: Through infrastructure as code reuse, organizations reduce the cognitive load associated with onboarding new talent and retain that talent longer by improving productivity for team members.
5. Optimize cloud cost: By implementing a central shared service for provisioning, you will be able to optimize cloud spend and costs. This is achieved by standardizing and enforcing best practices on providing visibility into what is being provisioned across the organization. While details on how to do this and implement the necessary guardrails is covered in later HVDs, this guide is a necessary prerequisite towards that goal.

Functional objectives

1. Adopt a mature golden workflow for infrastructure provisioning.
2. Enhance security posture.
3. Improve traceability of actions and ensure audit readiness.

Onboarding/adoption checklist

We recommend that the following tasks be accomplished for a successful onboarding and adoption of HCP Terraform/Enterprise. The time it takes to complete this initial phase will vary depending on the complexity of your organization and the level of executive alignment. However, we have found that using HashiCorp Professional Services or partner-provided services can significantly accelerate the process.

Project checklist

1. Identify key people from the Platform Team who will own and operate Terraform. In your organization, the Platform Team may own the architecture but the day-to-day operations may be delegated to a production services/support team who have 24/7 staffing arrangements. Both teams must be engaged at the outset.
2. Identify key executives sponsoring this project.
3. Establish cadences with the HashiCorp account team. We recommend the following:
   • Weekly/bi-weekly cadence.
   • Quarterly business review with sponsoring executives.
4. Enablement plan:
   • Platform Team enablement plan: We recommend that key platform team members attend HashiCorp Academy training. This training will also enable the Platform Team to be trained as trainers for the organization.
   • Application team enablement plan: We recommend that application teams be trained either by the Platform Team "trainers" or attend free hands-on workshops offered by HashiCorp solution engineers and architects.
5. Business unit onboarding schedule: Create a schedule for onboarding business units and/or application teams. We recommend for the "adopt" phase that you start with one or a handful of business units. (see note below)
6. Establish key milestones to track progress. We recommend the following key milestones:
   • HCP Terraform onboarding.
   • Platform team enablement.
   • Application team early-adopter enablement.
   • Application team early-adopter onboarding.

Onboarding checklist

1. Establish core integrations:
   1. VCS
   2. SSO/IdP
   3. HCP Terraform agents (optional)
   4. System logs and metrics (for Terraform Enterprise)
   5. HCP Terraform agent logs and metrics (optional)
   6. Audit logs
2. Establish a workflow to onboard application teams to HCP Terraform/Enterprise:
   • Workflow vending
   • Cloud credentials for workspaces
3. Test of initial end-to-end CLI-driven run.
4. Test of end-to-end VCS-driven run.
5. Test SSO for the Platform Team and application teams.
6. Initial discussions with first set of early adopter teams regarding user onboarding experience and updates to the project backlog with next step improvements

Adoption checklist

1. Determine the consumption model most suited for your organization.
2. Establish a GitOps-based workflow for application teams. This should map to your existing organizational git repository standards.
3. Branching strategy: Decide on the branching strategy for managing environments.
4. Complete an adoption maturity assessment with a HashiCorp solution architect.