Uploaded image for project: 'Operator Ecosystem'
  1. Operator Ecosystem
  2. OPECO-2277

Add validation to ensure CSV names have the expected format

XMLWordPrintable

    • Icon: Task Task
    • Resolution: Won't Do
    • Icon: Undefined Undefined
    • None
    • None
    • None
    • 3
    • False
    • None
    • False
    • Operator SDK
    • Refinement Backlog

      The good practices validator should ensure that CSV names are in the form of `$operatorname.v.$majorversion.$minorversion.$patchversion`. The version itself cannot be validated against the CSV version field because Kubernetes resource name restrictions prevent compatibility with the semver spec.

      Community Issue: operator-framework/api#237

              Unassigned Unassigned
              ryking@redhat.com Ryan King (Inactive)
              Kevin Rizza
              Camila Macedo Camila Macedo
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

                Created:
                Updated:
                Resolved: