Skip to main content

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:

We support multiple connectors with different hostname for a single git provider to fetch catalog-info.yaml at once. Eg., 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.

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 only support secrets stored in the Harness secret manager.

Template Actions to Trigger Harness Pipeline​

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.