Skip to content

Validate OCM-Component-Descriptors #1107

Open
@ccwienk

Description

@ccwienk

Context / Motivation

ocm (+ cnudie) package offers a rather lowlevel binding for (de-)serialising OCM-Component-Descriptors, which merely covers basic syntactical checks. This may lead to invalid OCM-Component-Descriptors being created, either from Concourse-Pipeline-Template (using either component-descriptor trait, or (new) github-actions (defined in this repository)). This can lead to follow-up errors "downstream", fixing of which is time-consuming. We should therefore improve (and enforce) validation to catch errors prior to publishing of OCM-Component-Descriptors.

Implementation Proposal

Checks

  • duplicate labels - labelnames must be unique per list (may merge if values are identical)
  • duplicate artefacts - artefact-IDs must be unique per list (may merge if values are identical)
  • creationTime timestamp format must adhere to RFC 3339 (if present)

integrate validation into

  • ocm package (as a re-usable API / CLI-Tool)
  • Concourse Pipeline Template
  • GitHub-Action(s)

Metadata

Metadata

Assignees

No one assigned

    Labels

    area/deliveryDelivery relatedarea/ipceiIPCEI (Important Project of Common European Interest)component/cicdContinuous integration/delivery (tooling and processes)kind/enhancementEnhancement, improvement, extension

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions