Allow the user to define CATs tests to run or to not run

[qu1queee]

Is your feature request related to a problem? Please describe. Yes, there is no flexibility during run time(installation/upgrade) to define the CATs test to run.

Describe the solution you'd like A feature flag that can hold a list of test to skip or to run

Describe alternatives you've considered None

Additional context None

[f0rmiga]

We can extend: https://github.com/cloudfoundry-incubator/kubecf/blob/2cf693c261b95fbb5f32e56f392876b8bea30390/deploy/helm/kubecf/values.yaml#L311-L319

instead of adding another feature flag. For now, you can achieve that with:

properties:
  acceptance-tests:
    acceptance-tests:
      acceptance_tests:
        include: '=ssh'
        ginkgo:
          nodes: 12
          extra_flags: -v
          flake_attempts: 2

(I added the ginkgo key above as an example of how to also tweak it)

[qu1queee]

@f0rmiga ok, seems then this issue is obsolete, pls feel free to close it. The ginkgo is not documented anywhere, shall we?

[f0rmiga]

I'll reopen this and suggest creating the specific keys under the following, as I mentioned on my previous message: https://github.com/cloudfoundry-incubator/kubecf/blob/2cf693c261b95fbb5f32e56f392876b8bea30390/deploy/helm/kubecf/values.yaml#L311-L319

@fargozhu If you could schedule this soon, it should be quick to implement.