Skip to content

feat: Add Harness GitOps entity support #29

Description

@dewan-ahmed

The CLI currently has no support for Harness GitOps. Users managing
GitOps Agents, Clusters, Repositories, Applications, and ApplicationSets
must use the UI or REST API directly.

Adding GitOps support to the CLI would enable users to manage the full
GitOps lifecycle from the terminal and unblock automation/agent use cases.

Suggestion:

Noun list get create update delete execute
gitops_agent ✓ (manifest)
gitops_cluster
gitops_repository
gitops_application ✓ (sync, refresh)
gitops_application_set ✓ (sync)

The gitops_ prefix avoids collision with the existing repository (Code) noun.

Metadata

Metadata

Labels

betaBeta version for Harness CLI 3.0

Type

No type

Fields

No fields configured for issues without a type.

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions