Consolidate FF/FME under unified IaC provider
long-term
P
Plum Kite
Currently, the product portfolio includes two distinct products: Feature Management and Experimentation (FME) and Feature Flags (FF). Each uses a different Terraform provider - FME relies on a third-party open-source provider, while FF uses Harness's native implementation.
The current FME provider has limitations that prevent fully automated management cycles, specifically around API-key-to-environment relationship coverage. As such, it would be beneficial to consolidate these products under a unified IaC provider.
Log In
D
Deepak Puthraya
Merged in a post:
Official Terraform integration
Johannes Liegl
Need to have API first, Terraform integration is important. Significant value to the customer as a whole. Third party integration currently isn't complete (tags missing). Some teams can't use FME until we have this.
D
Deepak Puthraya
Merged in a post:
Infrastructure as code - Terraform Support FME
I
Iram Khan
Customer would like to use support for Infrastructure as code (i.e. Terraform) for creating and controlling flags. They currently do that with another competitor today (LD) and would like to do the same with FME.
D
Deepak Puthraya
Merged in a post:
Infrastructure as Code Support for FME
H
Honeydew Horse
Since the migration to app.harness.io, the Split Terraform provider https://github.com/davidji99/terraform-provider-split no longer will work. We need a way to get configuration as code supported for FME resources.
d
david.karow
updated the status to
long-term
Z
Zircon blue Parrot
Check out the updates to the provider - there is now support for harness mode authentication! https://github.com/davidji99/terraform-provider-split