Feature Requests

Problem Statement GitHub auto-discovery integrations are currently scoped to a single GitHub organization. Customers with many orgs must manually create and maintain a separate integration for each one. For large enterprises with dozens/hundreds of orgs, this creates significant setup and maintenance overhead and slows catalog onboarding. Current Behavior One auto-discovery integration maps to exactly one GitHub org Each new org requires a fully separate integration to be configured Org-less repositories are not supported (excluded by design due to load time and scope concerns; not in scope for this request) Proposed Solution Allow a single GitHub auto-discovery integration to target multiple organizations: Multi-select or list-based org configuration within one integration Ability to add/remove orgs from an existing integration without recreating it Discovery, sync, and catalog population behavior identical to current single-org flow, applied per selected org

When running an API call to a non-existent entity, we see a return of all values, rather than a message that we are accessing an entity that doesn't exist. We need better indicators because. this is incredibly misleading.

Hi Team, Currently, We did not correctly show the status of long running steps in IDP. Steps will show as running even though it has finished execution. We would like IDP to report the correct status.

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.

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.