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. This page outlines all the supported integrations, providers, and features available in Harness IDP.
1. Git Providers
Harness IDP supports the following Git providers for storing and managing catalog entity definitions (catalog-info.yaml files) and workflow definitions:
| Git Provider | Support Type | Documentation |
|---|---|---|
| Harness Code Repository | Default | Learn more |
| GitHub | Cloud & Enterprise | Cloud | Enterprise |
| GitLab | Cloud & Self-Hosted | Learn more |
| Bitbucket | Cloud & Server | Learn more |
| Azure Repos | Cloud | Learn more |
Backstage doesn't support SSH auth type for integrations. Only HTTP connection is supported for all 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 the only supported method.
2. CI/CD Providers
Harness IDP is CI/CD agnostic and integrates with various CI/CD tools:
| CI/CD Provider | Support | Notes |
|---|---|---|
| Harness CI/CD | ✅ Fully Supported | Recommended for the best out-of-the-box experience |
| GitLab CI/CD | ✅ Supported | Works seamlessly with IDP workflows |
| GitHub Actions | ✅ Supported | Compatible with IDP orchestration |
| CircleCI | ✅ Supported | Can be integrated with IDP workflows |
| Jenkins | ✅ Supported | Compatible through pipeline triggers |
| Other CI/CD Tools | ✅ Supported | Any CI/CD tool that can be triggered via API/webhook |
Harness IDP requires some secrets to be set for plugins and external integrations in the Catalog to work. We support all types of secret managers for secure credential storage.
For information about what's supported for other Harness modules and the Harness Platform overall, refer to Supported platforms and technologies.
3. Harness IDP Plugins
Harness IDP supports a curated collection of plugins to integrate the software catalog with third-party providers and extend functionality:
| Plugin Type | Description | Documentation |
|---|---|---|
| Harness Native Plugins | Official plugins that integrate seamlessly with other Harness modules (CI/CD, Feature Flags, Chaos Engineering, STO, etc.) | View Harness Plugins |
| Backstage Community Plugins | Third-party and community plugins from the Backstage ecosystem | View Available Plugins |
| Custom Plugins | Build your own frontend plugins for specific use cases | Build Custom Plugins |
4. IDP Entities for Git Experience
Harness IDP Git Experience allows you to store and version control your IDP configurations in Git repositories. The following table shows which IDP entities support Git Experience:
| IDP Entity | Git Experience Support | Notes |
|---|---|---|
| Catalog Entities | ✅ Supported | Component, API, Resource, and other catalog entities can be stored as YAML files in Git |
| Workflows | ✅ Supported | Workflow definitions can be stored and tracked in Git repositories |
| Scorecards | ❌ Not Supported | Scorecards don't currently support Git Experience |
| Plugins | ❌ Not Supported | Plugin configurations don't currently support Git Experience |
| Layouts | ❌ Not Supported | Layout configurations don't currently support Git Experience |
5. Harness IDP Workflow Actions
Harness IDP Workflows use custom actions to trigger and orchestrate Harness Pipelines. The following workflow actions are supported:
5.1. trigger:harness-custom-pipeline
This action allows you to trigger Harness Pipelines directly from IDP workflows.
Supported Pipeline Types:
- IDP Stage
- Deploy Stage
- Custom Stage (Available with Harness CD License or Free Tier)
- Pipelines using Pipeline Templates
- Codebase-disabled Build Stage with Run step (Available with Harness CI License)
Requirements:
- All inputs, except for pipeline expressions, must be fixed values.
5.2. trigger:trigger-pipeline-with-webhook
This action triggers pipeline execution using webhook-based triggers.
Features:
- Supports all types of pipelines with webhook-based triggers
- Triggers pipeline execution based on input-set identifier and webhook name
Workflows in IDP use Harness Pipelines as orchestrators. Any secret requirements in workflows (e.g., write actions in Git providers) can be managed using:
- Third-party secret managers enabled through Delegates
- Harness Secret Manager
6. Miscellaneous
Additional features and capabilities supported in Harness IDP:
| Feature | Support Status | Details |
|---|---|---|
| Custom Plugins | ✅ Supported | We support only Frontend Backstage Plugins as Custom Plugins |
| Scorecard Data Sources | ✅ Supported | Multiple data sources available for scorecards. View all data sources |
| Backstage Plugins | ✅ Supported | Curated collection of Backstage plugins. View available plugins |
| Custom Theming and Branding | ❌ Not Supported | Custom theming is not currently available |
| Developer Homepage Customization | ✅ Supported | You can customize the Homepage for a personalized developer experience |
| API Support for Entity Updates | ✅ Supported | Ingestion APIs available to programmatically update catalog entities |
| Harness Delegate | ✅ Supported | Required for accessing private URLs and resources behind firewalls |
| Secret Managers | ✅ Supported | All types of secret managers are supported |