Uploaded image for project: 'OpenShift Service Mesh'
  1. OpenShift Service Mesh
  2. OSSM-4050

Type-safe helm values API

XMLWordPrintable

    • Icon: Story Story
    • Resolution: Done
    • Icon: Normal Normal
    • Sail MVP2
    • None
    • Sail Operator
    • None
    • Sprint 10, Sprint 11, Sprint 12, Sprint 13

      As a developer I would like to have type hints and autocompletion when writing my IstioHelmInstall CRD.

      Acceptance Criteria:

      • All fields in helm values API are defined with types in our CustomResourceDefinition
      • Ensure that new fields introduced upstream will be added
        • E.g. by adding a script that pulls all known values from the values.proto file and extends our CRD)
        • In a first iteration this could just be a script that fails if any field that is present in upstream’s values_types.proto is not present in our CRD
      • The `make gen` target should run this scripts

      -As we take on the Helm API, we should document the fields. Can we refer to the upstream doc or sync with it? Jamie would prefer not to document this if the information is upstream.

              _bmangoen Brian Mangoenpawiro
              rhn-support-tokeefe Tim O'Keefe
              Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

                Created:
                Updated:
                Resolved: