Feature Requests

we are Integrating Dynatrace with IDP components so we need components list in dropdown for particular loggedin user in template UI to select particular component to update, for that we only show them list of componets which has user permission to update not all components list.

Currently the Git Clone step suppprts using a connector with GitHub using GitHub App authentication. The Direct push only supports using username and password and not GitHub App auth.

As part of catalog onboarding, perhaps via a utility ingestion, it should auto discover all the pipelines associated with the service (CI CD), and services. It could speed up onboarding.

As a user , I would like to customize scorecard failure with a custom message , but also being able to evaluate an expression to fetch a metadata for the service to display the reason for failure. The reason for failure can come from ingestion process.

We kindly request the implementation of the Kubelog plugin for our IDP instance. This plugin will significantly enhance our ability to monitor and manage Kubernetes resources directly within IDP. Plugin Details: Name: Kubelog Plugin Purpose: Viewing Kubernetes logs and performing basic operations within Backstage Key Features: Browse Kubernetes logs of entities directly in Backstage Restart pods from the Backstage interface (available in version 0.9 and above) Integration with Kwirth for log exporting Benefits: Streamlined log viewing for developers Reduced complexity in managing Kubernetes resources Improved self-service capabilities for development teams We appreciate your assistance in implementing this plugin to enhance our IDP functionality and Kubernetes management capabilities

Currently, user has to click the dropdown and select the desired value from the list. What needs to be done, to have the first value as default value, as this will avoid clicking and opening of the dropdown list.

Currently we are able to pull out org or project details in IDP, but a capability to select repo's based on a project would be more helpful for couple of self-services.

Currently, when a pipeline triggered via the Internal Development Portal fails, the only output the user is met with is "Pipeline Failed!". The user needs to see more meaningful logs to be able to understand why a pipeline failed. Especially if that user does not have access to the underlying pipeline.

We would like to have a plugin to integrate Ardoq into IDP to show relationship data in a UI card/tab. Ardoq is our source-of-truth for technology portfolio management and ownership information is already documented there. It would save us time if we could export and render this info in a view like the Catalog graph for entity relations.

We would like to have the same functionality as seen in the Pagerduty plugin for xMatters, which is the service reliability platform we use.