[Tracker] : Breaking Changes in API

[shubham-cmyk]

A tracker to collect the breaking changes in API's in the next major release.

• resource -> check in

  chainsaw/pkg/apis/v1alpha1/file_ref_or_check.go

  Line 11 in b01fe35

  Resource *Check `json:"resource,omitempty"`

• namespace -> change to a struct

  chainsaw/pkg/apis/v1alpha1/test_spec.go

  Line 31 in 3f81244

  Namespace string `json:"namespace,omitempty"`

• add metadata to mimick structure of an object

  chainsaw/pkg/apis/v1alpha1/object_reference.go

  Line 8 in 3f81244

  ObjectSelector `json:",inline"`

• separate test and config in two different groups
• rename podLogs -> logs
• group report fields
• remove TestStep CRD
• support file in delete

[chipzoller]

You may want to standardize on how to refer to existing cluster resources across all operations so you avoid having to do this:

  - name: 04 - Delete good PDBs
    try:
    - delete:
        ref:
          apiVersion: policy/v1
          kind: PodDisruptionBudget
          name: good-pdb01
  - name: 05 - Update existing Deployments to have one replica
    try:
    - patch:
        resource:
          apiVersion: apps/v1
          kind: Deployment
          metadata:
            name: alpha-busybox
          spec:
            replicas: 1

Note ref versus resource when both operations refer to an existing cluster resource.

[eddycharly]

separate test and config in two different groups

i don't remember why we wanted that 🤔