Docker Artifacts

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.