Skip to content

Reduce severity for version validation in ocm get cv from error to warning #752

@morri-son

Description

@morri-son

Description
Related to #743 this issue is about reducing the severity for failures based on version validation in ocm get from error to warning. That will enable someone dealing with a component version that has an invalid version to at least use ocm get cv and inspect the component version.

Done Criteria

  • ocm get cvable to handle invalid versions, only throwing a warning, not an error.
  • Code has been reviewed by other team members
  • Analysis of existing tests (Unit and Integration)
  • Unit Tests created for new code or existing Unit Tests updated
  • Integration Test Suite updated (includes deletion of existing unnecessary Integration Test and/or creation of new ones if required)
  • Enduser Documentation updated (if applicable)
  • Internal technical Documentation created/updated (if applicable)
  • Successful demonstration in Review

Metadata

Metadata

Assignees

Labels

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

Type

No fields configured for Bug.

Projects

Status
🍺 Done

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions