100% Remote: HashiCorp Consultant role opens with my client

Hello, I have an exclusive position with my client below. Please let me know if you're interested so we can move forward. Job Title: HashiCorp Consultant Location: 100% Remote Duration: 6+ months Contract Description of position: • HashiCorp Resident Services is engaged with client to provide technical enablement and to accelerate their adoption of Terraform Enterprise. In addition to our Resident Architect guiding them through their onboarding and migration process, they are concerned about ensuring a level of engineering support from HashiCorp or a partner of Hashi, to address upcoming project deadlines. While our Residency team brings specialized expertise to enablement and best practices, we are not structured as a traditional on-demand services group with the capacity to rapidly scale up headcount for short-term engagements. • Specifically, the migration / importing effort centers on consolidating disparate Terraform Open-Source workloads, Azure ARM templates, and AWS Powershell scripts currently deployed across their environment. The desired outcome is to ingest all of these into a unified version-controlled Git repository, with all infrastructure migrated and standardized as Terraform Enterprise-managed configurations. Notes: Terraform Enterprise Migration - Technical Notes What They Currently Have • Open Source Terraform - using across AWS, Azure, Google Cloud Platform, on-prem • AWS CloudFormation - currently converting to Terraform • Azure ARM Templates - also converting to Terraform • PowerShell scripts - converting those into Ansible Migration Target • Moving from open source into TFE on-prem (Terraform Enterprise on-premises) What They Need to Do For Open Source Terraform: • Migrating that state into Terraform • Importing the open source Terraform state For AWS/Azure Resources: • Writing Terraform code in say AWS, getting those things into the state • Writing Terraform for Azure and importing those resources • Every single piece of infrastructure they have in AWS and Azure...needs to be imported into a Terraform state • They have to go then write a bunch of scripts that are going to go out and query each individual resource Azure bucket - needs to crawl that resource, find out what it is, then come back and import that into the Terraform state Repository and Workspace Setup: • Making sure there's a repo • Terraform workspace is going to have an associated repo That repo is associated with the Terraform workspace that has that state file Apply tot his job