Many organizations manage multiple environments (such as Development, QA, and Production) and would benefit from a native, declarative way to manage IDP plugin configuration and lifecycle as code.

Today, plugin configuration and enablement can be automated using the available REST APIs. However, this requires customers to build and maintain their own orchestration for version control, promotion, and synchronization across environments.

It would be valuable to provide first-class GitOps / Infrastructure-as-Code support for IDP plugins, allowing teams to manage plugin state in a declarative and version-controlled manner.

* Git-backed management of IDP plugin configuration.

* Declarative enablement and disablement of plugins.

* Native Git Experience integration for plugin configuration.

* Version-controlled plugin configuration with change history.

* Promotion workflows between environments (e.g. Development → QA → Production).

* Environment-specific configuration overrides.

* Support for Harness Secret references without exposing secret values.

* Drift detection between the desired configuration and the deployed configuration.

* Import/export of plugin configuration.

* Ability to synchronize plugin configuration consistently across multiple Harness environments.

A native declarative approach would allow teams to:

* Manage IDP configuration using Infrastructure-as-Code practices.

* Store plugin configuration alongside the rest of their platform configuration in source control.

* Promote changes through existing CI/CD approval workflows.

* Reduce manual administration and configuration drift.

* Improve auditability, repeatability, and rollback capabilities.

* Simplify onboarding and ongoing management of IDP across multiple environments.

The existing REST APIs provide the necessary building blocks to automate plugin enablement and configuration. However, customers must currently implement and maintain their own orchestration around these APIs to achieve GitOps or Infrastructure-as-Code workflows.