RFC: Official Terraform provider for MLflow resources

[a2105z]

Summary

Adds rfcs/0000-terraform-provider proposing an official Terraform provider (registry.terraform.io/mlflow/mlflow) for declarative MLflow control-plane resources.

Related issue: mlflow/mlflow#23202

What this RFC covers

• Problem reproduction: Terraform Registry has no mlflow/mlflow provider; imperative Python/REST APIs already work
• Decision to host mlflow/terraform-provider-mlflow (not inside the monorepo)
• Phased resources: Model Registry + Prompt Registry + webhooks → Deployments/Gateway endpoints → auth / Pulumi bridge
• Auth/TLS parity with the Python SDK env vars
• Import, secrets handling, compatibility matrix, and open questions for maintainers

Reproduction (abbreviated)

terraform init
# Error: provider registry.terraform.io does not have a provider named
# registry.terraform.io/mlflow/mlflow

Test plan

• Maintainer review of scope (Phase 1 resource set)
• Confirm Terraform Registry namespace / signing ownership
• Confirm whether mlflow_model_version stays out of Phase 1 (alias-only)
• Align with Pulumi community work (discussion #25049) on bridge follow-on

[a2105z]

Hi maintainers and reviewers — politely requesting review on this RFC when you have a chance.

Related issue: mlflow/mlflow#23202

CC:

• @TomeHirata (suggested the RFC path on the issue)
• @mprahl @B-Step62 @harupy @HumairAK (frequent RFC reviewers / core maintainers)
• @poudrouxj @harryfrzz @utkarshparekh @Jrojas-Baubap (interested parties from the issue / related Pulumi discussion)

Happy to iterate on scope, phasing, or open questions. Thank you for your time!