What's supported in Harness IDP

Harness Internal Developer Portal integrates with a number of third-party providers to provide a single pane of glass for developers.

Plugins for IDP

Harness IDP supports a number of plugins to integrate the software catalog with third-party providers. Please find the growing list of supported plugins. This is a subset of the Backstage plugin marketplace.

Any URLs behind any firewall or private URLs used in plugins should be accessed through Harness Delegate.

Git providers that IDP supports

Any software component can be registered in the catalog by using a YAML file stored in the following Git providers:

• Harness Code Repository (Default)
• GitHub
• GitLab
• Bitbucket
• Azure Repos

We support multiple connectors with different hostname for a single git provider to fetch catalog-info.yaml at once. E.g., Users can use connectors for both github.com and github enterprise and fetch entity YAML at the same time.

warning

Backstage doesn't support SSH auth type for integrations, hence only HTTP connection is supported for all the git provider based connectors in IDP.

API calls in IDP are used to fetch YAML data, last commit SHA, and detect any new changes. SSH authentication cannot be used for making these API calls; it is only used for cloning repositories. Therefore, the main Git connector for IDP Git integration must support API requests, hence HTTP is only supported

CI/CD providers that IDP supports

Harness IDP is agnostic to your CI/CD provider and works with tools such as GitLab, CircleCI, and GitHub Actions. You can use Harness CI/CD for a better out-of-the-box experience, but it's not required.

For information about what's supported for other Harness modules and the Harness Platform overall, refer to Supported platforms and technologies.

info

Harness IDP requires some secrets to be set for plugins and external integrations in Catalog to work. In these cases, we support all kind of secret managers.

Workflow Actions to Trigger Harness Pipeline

trigger:harness-custom-pipeline

• This action currently supports IDP Stage along with the Deploy Stage, Custom Stage(Available with Harness CD License or Free Tier usage), Pipelines using Pipeline Templates and codebase disabled Build Stage(Only Available with Harness CI License) with Run step.
• All input, except for pipeline expressions, must be fixed values.

trigger:trigger-pipeline-with-webhook

• This action supports all types of pipeline with a webhook based trigger. It triggers a pipeline execution based on the input-set identifier and a webhook name.

info

Workflows in IDP use Harness Pipelines as Orchestrator, so any secret requirement in workflows for eg., write action in git providers, can be added by using the third-party secret managers enabled through Delegates.

You can use Harness Secret Manager as well for the above described function.

Miscellaneous

What do we Support?	Links
Custom Plugins	We support only Frontend Backstage Plugins as Custom Plugins
Scorecard Data Sources	These are the list of available Scorecard Data Sources
Backstage Plugins	Available Backstage Plugins
Custom Theming And Branding	Not supported.
Developer Homepage Customisation	You can customize the Homepage for a personalized experience.
API support to update entities	We support Ingestion APIs to update entities in the catalog.