From f38a60740ad0e503b74d29c8954f73f801fef907 Mon Sep 17 00:00:00 2001 From: melindafekete Date: Wed, 30 Oct 2024 11:01:02 +0100 Subject: [PATCH] Initial --- website/docs/reference/terraform.mdx | 14 ++++++++++++++ 1 file changed, 14 insertions(+) create mode 100644 website/docs/reference/terraform.mdx diff --git a/website/docs/reference/terraform.mdx b/website/docs/reference/terraform.mdx new file mode 100644 index 0000000000..4b4c2ca640 --- /dev/null +++ b/website/docs/reference/terraform.mdx @@ -0,0 +1,14 @@ +--- +title: Using Unleash through Terraform +--- + +## Overview + +We'll look at managing an Unleash instance configuration through Terraform. Explore a typical Terraform workflow and how the unleash provider fits in with that. Look at the capabilities, setup requirements and best practices. + +Basic terraform configuration with the Unleash provider, execute a workflow to imoprt existing objects and create some new ones. + +Platform and devops teams managing projects and feature flags often have repetitive workflows locating specific configuration. Setting up permissions and manually inputting data. Domain specific knowledge requirements, needing familiarity with the UI. +Manual error, scalability issues, lack of version control. + +Terraform answer: condified configurations with Terrafor (replace conplex UI steps with structured code), standardized onboarding, minimizwed human error, scalability and consistency, clear audit trails. \ No newline at end of file