Skip to content

Create a plugin component version for Helm Input plugin #695

@Skarlso

Description

@Skarlso

Description

In #616 we decided to follow a component based registry approach.

This requires component constructors and a CI pipeline to publish a plugin into the open-component-model organization.

# Plugin Component: ocm.software/plugins/helminput:0.0.1
name: ocm.software/plugins/helminput
version: 0.0.1
provider: ocm.software
labels:
  - name: category
    value: input
  - name: registry
    value: official
  - name: description
    value: Official Helm Input plugin
resources:
  - name: binary                    # Plugin binary name
    type: ocmPlugin
    version: 0.0.1
    extraIdentity:
      architecture: amd64
      os: linux
    access:
      type: localBlob
      localReference: sha256:ac3f34...
  - name: binary
    type: ocmPlugin
    version: 0.0.1
    extraIdentity:
      architecture: amd64
      os: darwin
    access:
      type: localBlob
      localReference: sha256:f1764c...

Done Criteria

  • A pipeline exist that pushes a new component version for a new version of the helm input plugin upon release
  • A plugin component exists in the open-component-model organization's OCI registry
  • Enduser Documentation updated (if applicable)
  • Internal technical Documentation created/updated (if applicable)
  • Successful demonstration in Review

Metadata

Metadata

Labels

area/ipceiImportant Project of Common European Interestkind/tasksmall task, normally part of feature or epic

Type

No fields configured for Task.

Projects

Status
🍺 Done

Milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions