Uploaded image for project: 'OpenShift Pipelines'
  1. OpenShift Pipelines
  2. SRVKP-4387

Support both `string` and `bool`type for pipelinerun deep inspection field in Operator

XMLWordPrintable

    • 1
    • False
    • None
    • False
    • In tectonconfig spec.chain.artifacts.pipelinerun.enable-deep-inspection field now supports both bool and string value, before it only supported bool
    • Pipelines Sprint Pioneers 2, Pipelines Sprint Pioneers 3, Pipelines Sprint Pioneers 4, Pipelines Sprint Pioneers 5, Pipelines Sprint Pioneers 6, Pipelines Sprint Pioneers 7

      As of today the type for 

      Chain.spec.chain.artifacts.pipelinerun.enable-deep-inspection

      is a boolean pointer, but based on the this comment https://github.com/redhat-appstudio/infra-deployments/pull/3543#issuecomment-2040315963, we should support both type i.e. boolean and string in order to maintain the consistency and avoid the validation error for user for smooth usage

       

              rbehera-1 Rupali Behera
              ppunamiy Puneet Punamiya
              Puneet Punamiya Puneet Punamiya
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

                Created:
                Updated:
                Resolved: