Feature Requests

The harness_platform_idp_catalog_entity Terraform resource currently only accepts a fixed set of catalog kinds: component, group, user, workflow, resource, and system. Custom catalog entity kinds can be created successfully via the IDP UI, but cannot be managed through Terraform due to this validation restriction. Please add support for custom catalog entity kinds in the Terraform resource to align provider functionality with what is supported in the UI.

Please enable the IDP_2_0 feature flag for account nPYQjrqZTXaBlyk50fEBoA and verify IDP is provisioned for the account. IDP is missing from the module switcher; /ng/account/nPYQjrqZTXaBlyk50fEBoA/module/idp redirects to a blank trial page, and the IDP frontend assets fail to load.

Problem Statement Our API Platform and API Governance teams are leveraging Harness IDP as the strategic enterprise developer portal for API discovery, cataloging, governance, and self-service developer enablement. While Harness IDP provides strong catalog capabilities, it currently lacks support for two key GraphQL ecosystem plugins commonly available in Backstage: Apollo Explorer GraphQL Voyager These plugins are currently not enabled/supported within Harness IDP and require custom implementation or external tooling. This creates a fragmented developer experience and limits the ability of application teams to discover, understand, validate, and consume GraphQL APIs directly within the IDP experience.

Problem: The IDP Grafana plugin does not fully support AWS Managed Grafana when Unified Alerting is enabled (unifiedAlerting: true): Alert display (grafana/alert-label-selector) – The plugin queries Grafana's Unified Alerting ruler API and receives a successful (HTTP 200) response, but fails to surface matching alerts in the IDP Grafana tab, even when the alert is actively firing with a label that matches the selector. Other Grafana queries (e.g. dashboard tag search) work correctly through the same proxy path, indicating the issue lies in how the plugin parses/filters the Unified Alerting response — potentially due to a structural difference in AWS Managed Grafana's API output. Dashboard embedding (grafana/overview-dashboard) – Embedded dashboards load directly in the browser (not through the Delegate Proxy), which triggers Grafana's login redirect and gets blocked by its Content-Security-Policy, resulting in a failed embed. This suggests the current embedding approach doesn't account for Grafana environments requiring authenticated/proxied access. Ask: Add/fix support for parsing Unified Alerting responses from AWS Managed Grafana so label-matched alerts render correctly in IDP. Support an authenticated or proxied embedding mechanism for grafana/overview-dashboard that works with Grafana instances enforcing login and CSP restrictions (such as AWS Managed Grafana). Impact: Without this, customers using AWS Managed Grafana cannot reliably use IDP's Grafana alert and dashboard-embed features, limiting IDP's Grafana integration to a subset of supported Grafana deployments.

When building multi-step IDP Software Templates, a later step's SelectFieldFromApi field (an API-populated dropdown, including multi-select checkbox lists) can't pre-check the options that match values already stored in form context from an earlier step. The field loads its full option list from the API correctly, but any matching value(s) captured earlier in the workflow aren't automatically selected, so users have to manually re-select items they already provided. This shows up most in re-run or edit workflows: a user picks a set of resources in one step, that selection is saved to context, and a later step's picker (backed by the same or a related API) should come in with those same items already checked so the user only needs to add or remove entries rather than re-picking everything from scratch. Supporting this for both single-select and multi-select configurations would remove a real point of friction in multi-step catalog and resource-management workflows.

Env Management: Provide the ability to retry the deployment for a specific entity directly, rather than only having the option to run a full deployment failure retry.

Environment Management : When clicking on an entity in the Chart tab, display information or actionable options regarding that entity, similar to the view provided in the Resources tab.

Currently, the user experience for a developer to leverage IDP in order to take advantage of Harness' shift-left capability with IDP+CI+STO is 1) log into IDP 2)see a vulnerability in IDP (The Vulnerabilities tab for a service) 3) Map the vulnerability to a pipeline execution in the CI/CD tab and click into it 4) Click into vulnerabilities tab of the particular pipeline execution 5) Click into the same vulnerability they saw in step 2 6) Finally click "Create PR" or gain access to AI recommended fix It would be great to be able to go from step 2 to step 6 while staying in IDP. Or, surface a hyperlink that maps the IDP "Vulnerabilities" tab scan results to pipeline execution's vulnerability tab.

Currently there are many manual clickops are required when deploying IDP components into Production: IDP layout Plugin config and setup (native & custom plugin) Scorecard configuration Workflows creation SSEM (self service environment management) To avoid the issues with manual configuration, it would be great if Harness can have a mechanism to automate the promotion of config/setup to Prod in an automated manner.

Problem: Currently, Harness Resource Groups support "By Tag" for Pipelines, but this option is not available for Catalog (IDP) entities. Request: Add a By Tag option for the Catalog resource so access to IDP entities can be managed based on tags.