support path key prefix selection in Config

[cwlbraa]

I'd like to write a rebase rule that always pulls all of the cert-manager.io/ annotations for secrets out of the cluster, but right now I think I have to write that like this:

rebaseRules:
- path: [metadata, annotations, "cert-manager.io/alt-names"]
  type: copy
  sources: [new, existing]
  resourceMatchers: &opaqueSecrets
  - apiVersionKindMatcher: {apiVersion: v1, kind: Secret, type: Opaque}

- path: [metadata, annotations, "cert-manager.io/certificate-name"]
  type: copy
  sources: [new, existing]
  resourceMatchers: *opaqueSecrets

- path: [metadata, annotations, "cert-manager.io/common-name"]
  type: copy
  sources: [new, existing]
  resourceMatchers: *opaqueSecrets

- path: [metadata, annotations, "cert-manager.io/ip-sans"]
  type: copy
  sources: [new, existing]
  resourceMatchers: *opaqueSecrets

- path: [metadata, annotations, "cert-manager.io/issuer-kind"]
  type: copy
  sources: [new, existing]
  resourceMatchers: *opaqueSecrets

- path: [metadata, annotations, "cert-manager.io/issuer-name"]
  type: copy
  sources: [new, existing]
  resourceMatchers: *opaqueSecrets

- path: [metadata, annotations, "cert-manager.io/uri-sans"]
  type: copy
  sources: [new, existing]
  resourceMatchers: *opaqueSecrets

when really what I want is something like:

rebaseRules:
- path: [metadata, annotations, {prefixed: "cert-manager.io/"}]
  type: copy
  sources: [new, existing]
  - apiVersionKindMatcher: {apiVersion: v1, kind: Secret, type: Opaque}

Tasks

• rebase rules to support regex as new field in config path
• diff stage to support new field. changes in (mod_field_copy, remove, overlay_contract mod - resources package)
• test ownership rules, label scoping rule
• e2e test case
• documentation

[sethiyash]

Here is the Proposal on the different approaches which is still in the discussion phase.

[sethiyash]

Internally we decide to start supporting regex in path similar to the allIndexes we had earlier.

- path: [metadata, annotations, {regex: "^cert-manager[.]io"}]

The regex key will take the regular expression supported by Golang as a value. Please let us know your thoughts.
cc: @cwlbraa

[renuy]

Available as part of 0.59.0.
Please confirm once, closing this issue