Harness Feature Flags

Plugin details
Created by	Harness
Category	Feature flags
Source	GitHub
Type	Open-source plugin

Configuration

Application configuration YAML

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:

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

Secrets

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

Delegate proxy

No action required

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

Layout

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. Go to Admin > Layout, select Service in the dropdown menu, and then add the following YAML code in a new Feature Flags section:

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

The isHarnessFeatureFlagAvailable condition is met when the harness.io/project-url annotation is present in the software components's catalog-info.yaml definition file.

Annotations

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:

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

Support

The plugin is owned by Harness and managed in the Harness plugins repository as an open-source project. Create a GitHub issue to report bugs or suggest new features for the plugin.