Remove paths field from update.setters

The paths field in update.setters is to restrict the update to files
in particular paths.

But this is not implemented, and although it sounds useful, it's not
clear it's necessary. Until there's a known problem to be solved by
it, I'm removing it.

Signed-off-by: Michael Bridgen <[email protected]>

Author: squaremo

api/v1alpha1/imageupdateautomation_types.go

@@ -73,11 +73,6 @@ type UpdateStrategy struct {
 // SettersStrategy specifies how to use kyaml setters to update the
 // git repository.
 type SettersStrategy struct {
-	// Paths gives all paths that should be subject to updates using
-	// setters. If missing, the path `.` (the root of the git
-	// repository) is assumed.
-	// +optional
-	Paths []string `json:"paths,omitempty"`
 }
 
 // CommitSpec specifies how to commit changes to the git repository

api/v1alpha1/zz_generated.deepcopy.go

@@ -97,14 +97,6 @@ spec:
                   setters:
                     description: Setters if present means update workloads using setters,
                       via fields marked in the files themselves.
-                    properties:
-                      paths:
-                        description: Paths gives all paths that should be subject
-                          to updates using setters. If missing, the path `.` (the
-                          root of the git repository) is assumed.
-                        items:
-                          type: string
-                        type: array
                     type: object
                 type: object
             required: