Feature Requests

We lack the ability to effectively customize and dynamically structure the main Catalog landing page to create a more curated and user-friendly experience tailored to our organization's needs.

We are having issues with object references in arrays. For example, when we have an object like a true/false box that is referred by a lower object with a conditional and these objects exist in an array, the lower object always appears at the bottom of the array instead of under the expected True/False object.

This enhancement is a huge pain point for teams. When working with objects/arrays with many parameters it becomes extremely cumbersome in the UI. As the parameters and objects increase the more difficult it becomes to manage them. We need to be able to hide/use like an accordion object with our arrays but still retain the data within them. The only way to “hide” arrays at this point is to delete the objects inside the arrays.

Users of IDP absolutely dislike having to enter data in one field and then go to another form to select the data from the API call. If we have 10 inputs that use API calls we will need another 10 input boxes to select from those API calls. For example with how search engines work, when you enter data do you enter in text box 1 and then go to a second text box to select the auto-completed suggestions and whatnot?

The list of icons in Layout -> Icons for IDP is very useful! It would be nice to also have "Chronosphere" icon for my IDP service page which has links to Chronosphere dashboards.

IDP Scorecards: Existing IDP scorecards only check a limited range of items (Git-based metrics, CI/CD success rates, etc.). This coverage is insufficient to convince app owners of IDP’s broader value. ScoreCards at AppCI level and not on service

Currently there is no way to filter entities registered in catalog based on date as there is no created date column. It will be nice if we have a column that shows the created date.

Currently, we have multiple IDP workflows that allow users to create Bitbucket repositories within respective projects based on user-entered values. However, there is no built-in mechanism to validate whether the entered repository name already exists before proceeding with creation. For example, in an IDP workflow, we have a field: "Enter the repository name to be created". We want to validate this user input against Bitbucket before the repository is created, preventing duplicate repositories. Current Workaround & Limitation: Harness IDP supports fetching API-driven options via SelectFieldFromApi, allowing users to pick from a list of existing repositories. However: SelectFieldFromApi only works when selecting from pre-fetched options. It does not validate a user-entered value in real-time.

Hello, Restrict Developers to view modules except assigned to them from Account Level/Project Level. The Landing page should be IDP as user login using SSO.

Plugin Development Custom Plugins is enabled but we can build only Front-end Plugins Backend plugin is not enabled and its a blocker to build any new custom plugins that we have to create No test environment of harness IDP to build and test Plugins