Closed clux closed 8 months ago
some counterpoints to this;
$action
and action
in the policy from comment)analyzer
and the output
module..maybe it is better to look for duplicate keys on the Container
side (as per comment) and if we find any duplicates, THEN remove duplicates instead.. EDIT: trying this in https://github.com/kube-rs/kopium/pull/206
After examining approaches, this PR here would force a hard-to-discover user opt-in to an inferior solution (with warnings generated) that would likely need further massaging on the user side to be nice.
Closing this in favour of https://github.com/kube-rs/kopium/pull/206 which is actually usable by default despite sometimes producing anachronistic member names.
Running kopium on the
PodMonitor
prometheus crd we encounter the strange enum that has two variants (with different cases) that by default produces this:we can now pass a substring of struct names to opt-out the rename behaviour so that if we run kopium here on podmonitors with:
we end up with a dumber enum that looks like:
of course, this will cause rust warnings for
non_camel_case_types
that will have to be ignored.