Pluralise FieldExport into many rather than one mapping #1887
Labels
area/field-export
Issues or PRs related to Field Export
kind/enhancement
Categorizes issue or PR as related to existing feature enhancements.
needs-priority
Indicates a PR lacks a `priority/foo` label and requires one.
Is your feature request related to a problem?
Currently I need to have multiple field exports for objects created by ACK, and resources created with more usable and pertinent data fields incur even more field exports.
Describe the solution you'd like
Allow FieldExport to take an array of field exports to minimise the object count. Either an array top level on the
.spec
or nested under.spec.exports
should the need to add additional configuration come up. Could extrapolate the.spec.to.name
and.spec.to.kind
to a shared key in the spec and only denote only the.spec.to.key
spec per field export, but that may be over optimisation.Describe alternatives you've considered
Multiple FieldExports for objects with multiple fields I wish to map to a configmap/secret.
The text was updated successfully, but these errors were encountered: