> 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/harness-platform/3.0/harness-cli/cli/supported-resources-and-actions.md).

# Supported resources and actions

A complete matrix of every resource the Harness CLI supports and which actions are available on each one.

A complete matrix of every resource the Harness CLI supports and which actions are available on each one.

This page provides a reference matrix of all resources supported by the Harness CLI and the actions available for each resource. Use it to verify whether a specific operation is supported before building scripts, integrations, or automation workflows.

For detailed examples, flags, and usage information, go to the module-specific pages linked throughout this guide.

## What you will learn

By the end of this page, you will know:

* Which resources are available in each CLI module.
* Which actions each resource supports (`list`, `get`, `create`, `update`, `delete`, `execute`, `push`, and `pull`).
* Which resources support multi-level scoping through the `--level` flag.
* How to interpret the create and update behavior types shown in the matrix.

## Before you begin

* **Harness CLI installed and authenticated:** Go to [Install and upgrade](https://developer.harness.io/harness-platform/3.0/harness-cli/cli/overview.md) and [Authenticate](https://developer.harness.io/harness-platform/3.0/harness-cli/cli/authenticate-the-harness-cli.md) for setup steps.
* **Interactive alternative:** Run `harness list noun --matrix` in your terminal to view the same information directly from your installed CLI version.

### Matrix legend

| Symbol | Meaning                                                                                                                    |
| ------ | -------------------------------------------------------------------------------------------------------------------------- |
| `✓`    | Action is supported                                                                                                        |
| `—`    | Action is not supported                                                                                                    |
| `L`    | Supports the `--level` flag for multi-scope resources (account, organization, or project)                                  |
| `S`    | Set-fields: Creates a resource using `--set key=value` or positional arguments                                             |
| `GTP`  | Get-then-put: Updates a resource by fetching the current state, applying `--set` or `--del` changes, and saving the result |
| `Y`    | YAML-native: Manages a resource through YAML files using `--file` or `-f`                                                  |

All `list` actions support pagination flags (`--limit`, `--offset`, `--all`, and `--count`) by default.

### Platform

The Platform module manages the Harness account hierarchy, role-based access control, connectors, secrets, delegates, and related administrative resources. These foundational resources are used throughout the Harness platform.

Go to [Platform commands](https://developer.harness.io/harness-platform/3.0/harness-cli/cli/harness-cli-commands/platform.md) for examples and detailed usage information.

| Resource          | list | get | create | update | delete | execute |
| ----------------- | ---- | --- | ------ | ------ | ------ | ------- |
| `account`         | —    | ✓   | —      | —      | —      | —       |
| `organization`    | ✓    | ✓   | S      | GTP    | ✓      | —       |
| `project`         | L    | ✓   | S      | GTP    | ✓      | —       |
| `user`            | L    | ✓   | —      | —      | —      | —       |
| `user_group`      | L    | ✓   | —      | —      | —      | —       |
| `service_account` | L    | ✓   | —      | —      | —      | —       |
| `role`            | L    | ✓   | —      | —      | —      | —       |
| `role_assignment` | L    | ✓   | —      | —      | —      | —       |
| `resource_group`  | L    | ✓   | —      | —      | —      | —       |
| `permission`      | ✓    | ✓   | —      | —      | —      | —       |
| `connector`       | L    | ✓   | S      | GTP    | ✓      | ✓       |
| `delegate`        | L    | ✓   | —      | —      | —      | —       |
| `delegate_token`  | ✓    | —   | ✓      | —      | ✓      | —       |
| `secret`          | L    | ✓   | S      | GTP    | ✓      | —       |
| `setting`         | L    | ✓   | —      | —      | —      | —       |
| `entity_usage`    | ✓    | —   | —      | —      | —      | —       |

### Continuous Delivery

The Continuous Delivery module manages pipelines, executions, triggers, templates, freeze windows, services, environments, infrastructure definitions, and service overrides.

Go to [Continuous Delivery commands](https://developer.harness.io/harness-platform/3.0/harness-cli/cli/harness-cli-commands/continuous-delivery.md) for examples and detailed usage information.

| Resource                      | list | get | create | update | delete | execute |
| ----------------------------- | ---- | --- | ------ | ------ | ------ | ------- |
| `pipeline`                    | ✓    | Y   | Y      | Y      | ✓      | ✓       |
| `pipeline:dynamic`            | —    | —   | —      | —      | —      | ✓       |
| `pipeline:input_set`          | —    | —   | —      | —      | —      | ✓       |
| `pipeline:summary`            | —    | ✓   | —      | —      | —      | —       |
| `pipeline_v1`                 | ✓    | ✓   | —      | —      | —      | —       |
| `execution`                   | ✓    | ✓   | —      | —      | —      | —       |
| `execution_step`              | ✓    | —   | —      | —      | —      | —       |
| `execution_log`               | ✓    | ✓   | —      | —      | —      | —       |
| `execution:abort`             | —    | —   | —      | —      | —      | ✓       |
| `execution:retry`             | —    | —   | —      | —      | —      | ✓       |
| `execution:retry_history`     | —    | ✓   | —      | —      | —      | —       |
| `trigger`                     | ✓    | ✓   | Y      | Y      | ✓      | —       |
| `input_set`                   | ✓    | ✓   | Y      | Y      | ✓      | —       |
| `runtime_input_template`      | —    | ✓   | —      | —      | —      | —       |
| `approval_instance`           | ✓    | ✓   | —      | —      | —      | —       |
| `approval_instance:approve`   | —    | —   | —      | —      | —      | ✓       |
| `approval_instance:reject`    | —    | —   | —      | —      | —      | ✓       |
| `template`                    | ✓    | ✓   | Y      | —      | —      | —       |
| `template_version`            | ✓    | ✓   | —      | Y      | ✓      | —       |
| `template_version:set-stable` | —    | —   | —      | ✓      | —      | —       |
| `freeze_window`               | L    | ✓   | —      | —      | —      | —       |
| `global_freeze`               | —    | ✓   | —      | —      | —      | —       |
| `service`                     | ✓    | ✓   | S      | GTP    | ✓      | —       |
| `environment`                 | ✓    | ✓   | S      | GTP    | ✓      | —       |
| `infrastructure`              | ✓    | ✓   | S      | GTP    | ✓      | —       |
| `service_override`            | ✓    | ✓   | S      | GTP    | ✓      | —       |

### Artifact Registry

The Artifact Registry module manages registries, artifacts, artifact versions, and metadata. It also provides specialized `push`, `pull`, and `execute` operations.

Go to [Artifact Registry commands](https://developer.harness.io/harness-platform/3.0/harness-cli/cli/harness-cli-commands/artifact-registry.md) for examples and detailed usage information.

| Resource                         | list | get | create | update | delete | execute | push     | pull |
| -------------------------------- | ---- | --- | ------ | ------ | ------ | ------- | -------- | ---- |
| `registry`                       | ✓    | ✓   | S      | —      | ✓      | ✓       | —        | —    |
| `registry:firewall_scan`         | —    | —   | —      | —      | —      | ✓       | —        | —    |
| `registry:migrate`               | —    | —   | —      | —      | —      | ✓       | —        | —    |
| `registry_metadata`              | —    | ✓   | —      | GTP    | —      | —       | —        | —    |
| `artifact`                       | ✓    | ✓   | —      | —      | ✓      | ✓       | Multiple | ✓    |
| `artifact:bulk`                  | —    | —   | —      | —      | ✓      | —       | —        | —    |
| `artifact_metadata`              | —    | ✓   | —      | GTP    | —      | —       | —        | —    |
| `artifact_version`               | ✓    | ✓   | —      | —      | ✓      | ✓       | —        | —    |
| `artifact_version:copy`          | —    | —   | —      | —      | —      | ✓       | —        | —    |
| `artifact_version:firewall_scan` | —    | —   | —      | —      | —      | ✓       | —        | —    |
| `artifact_version_metadata`      | —    | ✓   | —      | GTP    | —      | —       | —        | —    |
| `artifact:download`              | —    | —   | —      | —      | —      | ✓       | —        | —    |
| `artifact_file`                  | ✓    | —   | —      | —      | —      | —       | —        | —    |

The `push` column reads `Multiple` for `artifact` because each package format has its own qualified noun. The 18 supported formats are `artifact:generic`, `artifact:maven`, `artifact:npm`, `artifact:python`, `artifact:nuget`, `artifact:rpm`, `artifact:cargo`, `artifact:go`, `artifact:conda`, `artifact:dart`, `artifact:composer`, `artifact:ruby`, `artifact:swift`, `artifact:puppet`, `artifact:debian`, `artifact:conan`, `artifact:helm`, and `artifact:docker`.

The `execute` column on `artifact` covers the five package-manager install helpers: `artifact:npm_install`, `artifact:npm_ci`, `artifact:pip_install`, `artifact:mvn_install`, and `artifact:dotnet_restore`.

`harness configure registry` is a registry-level action that writes local package-manager client configuration. It does not map to one of the columns above.

### Infrastructure as Code Management

The Infrastructure as Code Management module manages Terraform and OpenTofu workspaces, Ansible hosts, inventories, and playbooks, and the module and provider registries.

Go to [Infrastructure as Code Management commands](https://developer.harness.io/harness-platform/3.0/harness-cli/cli/harness-cli-commands/infrastructure-as-code-management.md) for examples and detailed usage information.

| Resource          | list | get | execute |
| ----------------- | ---- | --- | ------- |
| `workspace`       | ✓    | ✓   | ✓       |
| `host`            | ✓    | ✓   | —       |
| `inventory`       | ✓    | ✓   | —       |
| `playbook`        | ✓    | ✓   | —       |
| `registry_module` | ✓    | ✓   | —       |
| `provider`        | ✓    | ✓   | —       |

Workspace `create`, `update`, and `delete` commands are planned for Harness CLI v3.1.

### Code Repository

The Code Repository module manages repositories, pull requests, reviewers and codeowners, AI review insights, branches, commits, tags, comments, and status checks.

Go to [Code Repository commands](https://developer.harness.io/harness-platform/3.0/harness-cli/cli/harness-cli-commands/code-repository.md) for examples and detailed usage information.

| Resource                | list | get | create | update | delete | execute |
| ----------------------- | ---- | --- | ------ | ------ | ------ | ------- |
| `repository`            | L    | ✓   | S      | GTP    | ✓      | —       |
| `pr`                    | ✓    | ✓   | S      | GTP    | —      | —       |
| `pr:mine`               | ✓    | —   | —      | —      | —      | —       |
| `pr:review_pending`     | ✓    | —   | —      | —      | —      | —       |
| `pr:merge`              | —    | —   | —      | —      | —      | ✓       |
| `pr:close`              | —    | —   | —      | —      | —      | ✓       |
| `pr:review`             | —    | —   | —      | —      | —      | ✓       |
| `pr:insight`            | —    | ✓   | —      | —      | —      | —       |
| `pr:review_group`       | —    | ✓   | —      | —      | —      | —       |
| `pr_suggested_reviewer` | ✓    | —   | —      | —      | —      | —       |
| `pr_suggested_label`    | ✓    | —   | —      | —      | —      | —       |
| `pr_success_criterion`  | ✓    | —   | —      | —      | —      | —       |
| `code_principal`        | ✓    | —   | —      | —      | —      | —       |
| `pr_reviewer`           | ✓    | —   | ✓      | —      | ✓      | —       |
| `pr_codeowner`          | ✓    | —   | —      | —      | —      | —       |
| `branch`                | ✓    | ✓   | S      | —      | ✓      | —       |
| `commit`                | ✓    | ✓   | —      | —      | —      | —       |
| `pr_commit`             | ✓    | —   | —      | —      | —      | —       |
| `tag`                   | ✓    | —   | S      | —      | ✓      | —       |
| `pr_activity`           | ✓    | —   | —      | —      | —      | —       |
| `pr_comment`            | ✓    | —   | Y      | GTP    | ✓      | —       |
| `pr_check`              | ✓    | —   | —      | —      | —      | —       |
| `pr_check:log`          | —    | ✓   | —      | —      | —      | —       |
| `commit_check`          | ✓    | —   | —      | —      | —      | —       |
| `repo_label`            | ✓    | —   | S      | GTP    | ✓      | —       |
| `pr_label`              | ✓    | —   | —      | —      | —      | —       |
| `repo_settings:aicr`    | —    | ✓   | Y      | GTP    | —      | —       |
| `repo_settings:general` | —    | ✓   | —      | —      | —      | —       |

### GitOps

The GitOps module manages Argo CD-backed agents, applications, destination clusters, source repositories, and ApplicationSets.

Go to [GitOps commands](https://developer.harness.io/harness-platform/3.0/harness-cli/cli/harness-cli-commands/gitops.md) for examples and detailed usage information.

| Resource                     | list | get | create | update | delete | execute |
| ---------------------------- | ---- | --- | ------ | ------ | ------ | ------- |
| `gitops_agent`               | ✓    | ✓   | S      | —      | ✓      | ✓       |
| `gitops_agent:install`       | —    | —   | —      | —      | —      | ✓       |
| `gitops_application`         | ✓    | ✓   | Y      | Y      | ✓      | ✓       |
| `gitops_application:sync`    | —    | —   | —      | —      | —      | ✓       |
| `gitops_application:refresh` | —    | —   | —      | —      | —      | ✓       |
| `gitops_cluster`             | ✓    | ✓   | Y      | Y      | ✓      | —       |
| `gitops_repository`          | ✓    | ✓   | Y      | Y      | ✓      | —       |
| `gitops_application_set`     | ✓    | ✓   | Y      | Y      | ✓      | —       |

### Harness Worker Agents

Harness Worker Agents are Harness-managed automation workers. The `agent` noun lives in the `platform` module.

Go to [Worker Agent commands](https://developer.harness.io/harness-platform/3.0/harness-cli/cli/harness-cli-commands/harness-worker-agents.md) for examples and detailed usage information.

| Resource | list | get | create | update | delete |
| -------- | ---- | --- | ------ | ------ | ------ |
| `agent`  | ✓    | ✓   | Y      | Y      | —      |

### Governance

The Governance module manages OPA-based policies, policy sets, and policy evaluations.

Go to [Governance commands](https://developer.harness.io/harness-platform/3.0/harness-cli/cli/harness-cli-commands/governance.md) for examples and detailed usage information.

| Resource            | list | get | create | update | delete |
| ------------------- | ---- | --- | ------ | ------ | ------ |
| `policy`            | ✓    | ✓   | S      | GTP    | ✓      |
| `policy_set`        | ✓    | ✓   | S      | GTP    | ✓      |
| `policy_evaluation` | ✓    | —   | —      | —      | —      |

### Audit

The Audit module provides read-only access to audit events across the Harness platform.

Go to [Audit commands](https://developer.harness.io/harness-platform/3.0/harness-cli/cli/harness-cli-commands/audit.md) for examples and detailed usage information.

| Resource      | list | get |
| ------------- | ---- | --- |
| `audit_event` | ✓    | ✓   |

### Resilience Testing

The Resilience Testing module manages load tests defined against your services, including JMeter, Locust, and k6 tools. A loadtest is a reusable definition; run it with `execute loadtest <id> --follow` to start a run and stream output until it finishes.

Go to [Resilience Testing commands](https://developer.harness.io/harness-platform/3.0/harness-cli/cli/harness-cli-commands/resilience-testing.md) for examples and detailed usage information.

| Resource                      | list | get | create | update | delete | execute |
| ----------------------------- | ---- | --- | ------ | ------ | ------ | ------- |
| `loadtest`                    | ✓    | ✓   | Y      | Y      | ✓      | ✓       |
| `loadtest:from_json`          | —    | —   | Y      | —      | —      | —       |
| `loadtest:from_template`      | —    | —   | Y      | —      | —      | —       |
| `loadtest:variables`          | ✓    | —   | —      | —      | —      | —       |
| `loadtest:sync`               | —    | —   | —      | —      | —      | ✓       |
| `loadtest_run`                | ✓    | ✓   | —      | GTP    | —      | —       |
| `loadtest_run:stop`           | —    | —   | —      | —      | —      | ✓       |
| `loadtest_run:rerun`          | —    | —   | —      | —      | —      | ✓       |
| `loadtest_run:summary`        | —    | ✓   | —      | —      | —      | —       |
| `loadtest_run:metrics`        | ✓    | —   | —      | —      | —      | —       |
| `loadtest_run:graph`          | ✓    | —   | —      | —      | —      | —       |
| `loadtest_run:requests`       | ✓    | —   | —      | —      | —      | —       |
| `loadtest_run:endpoints`      | ✓    | —   | —      | —      | —      | —       |
| `loadtest_script`             | —    | ✓   | —      | GTP    | —      | —       |
| `loadtest_script:revisions`   | ✓    | —   | —      | —      | —      | —       |
| `loadtest_script:revision`    | —    | ✓   | —      | —      | —      | —       |
| `loadtest_template`           | ✓    | ✓   | Y      | Y      | ✓      | —       |
| `loadtest_template:variables` | ✓    | —   | —      | —      | —      | —       |
| `loadtest_template:yaml`      | —    | ✓   | —      | —      | —      | —       |
| `loadtest_template_revision`  | ✓    | ✓   | Y      | —      | ✓      | —       |
| `composite_loadtest`          | ✓    | —   | S      | —      | —      | —       |
| `loadtest_usage`              | ✓    | ✓   | —      | —      | —      | —       |
| `loadtest_usage:report`       | —    | ✓   | —      | —      | —      | —       |

### Knowledge Graph

The Knowledge Graph module provides a queryable graph of Harness entities via the Harness Query Language (HQL). Use `execute hql:run` to query the graph and `execute hql:explain` to inspect query plans before running them.

Go to [Knowledge Graph commands](https://developer.harness.io/harness-platform/3.0/harness-cli/cli/harness-cli-commands/knowledge-graph.md) for examples and detailed usage information.

| Resource            | list | get | execute |
| ------------------- | ---- | --- | ------- |
| `kg:type`           | ✓    | ✓   | —       |
| `kg:queryable_type` | ✓    | —   | —       |
| `kg:related_type`   | ✓    | —   | —       |
| `kg:connection`     | ✓    | —   | —       |
| `hql:run`           | —    | —   | ✓       |
| `hql:validate`      | —    | —   | ✓       |
| `hql:explain`       | —    | —   | ✓       |
| `hql:grammar`       | —    | —   | ✓       |

### Feature Management & Experimentation

The FME module manages feature flags, segments, metrics, and their per-environment definitions. Segments require `--segment-type`, and `--env` takes the environment ID, not the name. The `change_request` resource requires CLI v3.10.0 or later.

Go to [FME commands](https://developer.harness.io/harness-platform/3.0/harness-cli/cli/harness-cli-commands/fme.md) for examples and detailed usage information.

| Resource                  | list | get | create | update | delete | execute |
| ------------------------- | :--: | :-: | :----: | :----: | :----: | :-----: |
| `feature_flag` (`ff`)     |   ✓  |  ✓  |    S   |    S   |    ✓   |    —    |
| `feature_flag:archive`    |   —  |  —  |    —   |    —   |    —   |    ✓    |
| `feature_flag:unarchive`  |   —  |  —  |    —   |    —   |    —   |    ✓    |
| `feature_flag:definition` |   ✓  |  ✓  |    ✓   |    S   |    ✓   |    —    |
| `feature_flag:kill`       |   —  |  —  |    —   |    —   |    —   |    ✓    |
| `feature_flag:restore`    |   —  |  —  |    —   |    —   |    —   |    ✓    |
| `feature_flag:reallocate` |   —  |  —  |    —   |    —   |    —   |    ✓    |
| `fme_environment`         |   ✓  |  ✓  |    S   |    S   |    ✓   |    —    |
| `segment` (`seg`)         |   ✓  |  ✓  |    S   |    S   |    ✓   |    —    |
| `segment:definition`      |   ✓  |  ✓  |    ✓   |    S   |    ✓   |    —    |
| `metric`                  |   ✓  |  ✓  |    S   |    S   |    ✓   |    —    |
| `event_type`              |   ✓  |  ✓  |    —   |    —   |    —   |    —    |
| `traffic_type`            |   ✓  |  —  |    —   |    —   |    —   |    —    |
| `rollout_status`          |   ✓  |  —  |    —   |    —   |    —   |    —    |
| `change_request`          |   ✓  |  —  |    —   |    —   |    —   |    —    |

### Troubleshooting

* **A resource shows `—` for an action you expect to work:** The matrix reflects what the CLI currently supports; an action marked `—` is not implemented for that resource.
* **A `create` or `update` command fails even though the matrix shows `S`, `GTP`, or `Y` support:** Confirm you are using the expected input method for that resource (`--set key=value`, a get-then-put flow, or a `--file`/`-f` YAML payload), since each resource supports only the method shown in its column.
* **A resource you expect to find is missing from this matrix:** Run `harness list noun --matrix` from your installed CLI to confirm the resource and action set available in your current CLI version, since the matrix can lag a new CLI release.

### Related articles

These pages provide further reference material for working with the Harness CLI:

* [Global flags and output](https://developer.harness.io/harness-platform/3.0/harness-cli/cli/global-flags-and-output-formats.md): Review shared flags, output formats, filtering, and pagination.
* [Platform commands](https://developer.harness.io/harness-platform/3.0/harness-cli/cli/harness-cli-commands/platform.md): Manage accounts, RBAC, connectors, and secrets.
* [Continuous Delivery commands](https://developer.harness.io/harness-platform/3.0/harness-cli/cli/harness-cli-commands/continuous-delivery.md): Run pipeline and deployment workflows.
