> For the complete documentation index, see [llms.txt](https://developer.harness.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://developer.harness.io/internal-developer-portal/use-idp/plugins/available-plugins/harness-native-plugins/harness-feature-flags.md).

# Feature Flags

| Plugin details |                                                        |
| -------------- | ------------------------------------------------------ |
| **Created by** | Harness                                                |
| **Category**   | Feature flags                                          |
| **Source**     | [GitHub](https://github.com/harness/backstage-plugins) |
| **Type**       | Open-source plugin                                     |

## Configuration <a href="#configuration" id="configuration"></a>

### Application configuration YAML <a href="#application-configuration-yaml" id="application-configuration-yaml"></a>

*No action required*

This plugin requires a backend proxy configuration to make calls to Harness APIs with authentication. The following configuration is set by default and you do not need to change anything:

```yaml
proxy:
  "/harness/prod":
    target: "https://app.harness.io/"
    pathRewrite:
      "/api/proxy/harness/prod/?": "/"
    allowedHeaders:
      - authorization
```

### Secrets <a href="#secrets" id="secrets"></a>

No secrets are required for this plugin because both IDP and Feature Flags are part of the Harness software delivery platform.

### Delegate proxy <a href="#delegate-proxy" id="delegate-proxy"></a>

*No action required*

This plugin does not require a delegate proxy to be set up.

## Layout <a href="#layout" id="layout"></a>

*No action required*

This plugin exports a UI tab that you can use as a new Feature Flags tab for a service or for any other layout page. The following configuration is set by default in **Layout** under **Configure** for **Service** and you do not need to change anything:

```yaml
- name: feature-flags
  path: /feature-flags
  title: Feature Flags
  contents:
    - component: EntityHarnessFeatureFlagContent
```

Also, you could add a conditional like `isHarnessFeatureFlagAvailable` which is met when the `harness.io/project-url` annotation is present in the software component's `catalog-info.yaml` definition file.

```yaml
- name: feature-flags
  path: /feature-flags
  title: Feature Flags
  contents:
    - component: EntitySwitch
      specs:
        cases:
          - if: isHarnessFeatureFlagAvailable
            content:
              component: EntityHarnessFeatureFlagContent
```

![](/files/u6XfslMbWwCA1m1iAERQ)

## Annotations <a href="#annotations" id="annotations"></a>

To configure the plugin for a service in the software catalog, set one or both of the following annotations in its `catalog-info.yaml` definition file:

```yaml
apiVersion: backstage.io/v1alpha1
kind: Component
metadata:
  # ...
  annotations:
    # mandatory annotation
    harness.io/project-url: <harness_project_url>
spec:
  type: service
  # ...
```

## Support <a href="#support" id="support"></a>

The plugin is owned by Harness and managed in the [Harness plugins repository](https://github.com/harness/backstage-plugins) as an open-source project. Create a GitHub issue to report bugs or suggest new features for the plugin.