Helm Artifacts

APIs to get details of helm artifacts

Describe Helm Artifact Detail

Get Helm Artifact Details

Securityx-api-key
Request
path Parameters
registry_ref
required
string

Reference to the scope in which the registry exists.

Format depends on the scope:

  • Account-level: account_id/registry_name/+
  • Organization-level: account_id/org_id/registry_name/+
  • Project-level: account_id/org_id/project_id/registry_name/+

The /+ suffix is used internally to route scoped requests. It must be included exactly as shown in the URL.

Examples:
Only account ID, scoped at account level
acc123/registry123/+
Account and org ID, scoped at org level
acc123/org456/registry123/+
Account, org, and project ID, scoped at project level
acc123/org456/proj789/registry123/+
artifact
required
string

Name of the artifact.

The value depends on whether the name contains a slash (/):

  • If the artifact name contains /, append a trailing /+ at the end.
    • Example: mygroup/myartifact/+
  • If the artifact name does not contain /, use the plain name.
    • Example: myartifact

This is used internally to distinguish between namespaced and flat artifact names.

Examples:
myartifact
mygroup/myartifact/+
version
required
string

Name of Artifact Version.

Responses
200

response to get helm artifact detail

400

Bad request

401

Unauthenticated

403

Unauthorized

404

The specified resource was not found

500

Internal server error

get/har/api/v1/registry/{registry_ref}/artifact/{artifact}/version/{version}/helm/details
Request samples
Response samples
application/json
{
  • "data": {
    },
  • "status": "SUCCESS"
}

Describe Helm Artifact Manifest

Get Helm Artifact Manifest

Securityx-api-key
Request
path Parameters
registry_ref
required
string

Reference to the scope in which the registry exists.

Format depends on the scope:

  • Account-level: account_id/registry_name/+
  • Organization-level: account_id/org_id/registry_name/+
  • Project-level: account_id/org_id/project_id/registry_name/+

The /+ suffix is used internally to route scoped requests. It must be included exactly as shown in the URL.

Examples:
Only account ID, scoped at account level
acc123/registry123/+
Account and org ID, scoped at org level
acc123/org456/registry123/+
Account, org, and project ID, scoped at project level
acc123/org456/proj789/registry123/+
artifact
required
string

Name of the artifact.

The value depends on whether the name contains a slash (/):

  • If the artifact name contains /, append a trailing /+ at the end.
    • Example: mygroup/myartifact/+
  • If the artifact name does not contain /, use the plain name.
    • Example: myartifact

This is used internally to distinguish between namespaced and flat artifact names.

Examples:
myartifact
mygroup/myartifact/+
version
required
string

Name of Artifact Version.

Responses
200

response to get helm artifact manifest

400

Bad request

401

Unauthenticated

403

Unauthorized

404

The specified resource was not found

500

Internal server error

get/har/api/v1/registry/{registry_ref}/artifact/{artifact}/version/{version}/helm/manifest
Request samples
Response samples
application/json
{
  • "data": {
    },
  • "status": "SUCCESS"
}