stopPodsHostAction results in schema validation error

[Chris Stanaway]

Running seal 3.1.0.

Using example scenario from https://powerfulseal.github.io/powerfulseal/stop-host-running-a-pod.

Getting schema validation error.

$ cat test-scenario4.yaml
apiVersion: powerfulseal.io/v1
kind: Scenario
metadata:
  name: test-scenario4
spec:
  name: Stop that host!
  steps:
  - podAction:
      matches:
        - namespace: chris-dev
      filters:
        - randomSample:
            size: 1
      actions:
        - stopHost:
            autoRestart: true
  - wait:
      seconds: 30
$ kubectl apply -f test-scenario4.yaml -n chris-dev
The Scenario "test-scenario4" is invalid:
* : Invalid value: "": "spec.steps" must validate one and only one schema (oneOf). Found none valid
* : Invalid value: "": "spec.steps.podAction.actions" must validate one and only one schema (oneOf). Found none valid
* spec.steps.podAction.actions.kill: Required value
* ```

No issues with other `podAction.actions` - just `stopHost`. Verified that this action appears to be part of the 3.1.0 schema.

[Chris Stanaway]

Turns out that while the stopHost action is defined in ps-schema.yaml, it is not defined in the Scenario CRD https://github.com/powerfulseal/powerfulseal/blob/master/kubernetes/crd.yml.

[Chris Stanaway]

In addition, the cloneAction action is also not defined in the Scenario CRD.