Support replacing prefixes/suffixes #5722
Labels
kind/feature
Categorizes issue or PR as related to a new feature.
lifecycle/stale
Denotes an issue or PR has remained open with no activity and has become stale.
needs-triage
Indicates an issue or PR lacks a `triage/foo` label and requires one.
Eschewed features
What would you like to have added?
Currently we can add prefixes or suffixes. However, we cannot replace existing ones.
Why is this needed?
A convention I've seen in manifests is that cluster-wide resources are prefixed/suffixed, usually with the namespace used in namespace-scoped resources in the same manifest. For example, you may have a
Role
namedbar
in the namespacefoo
and a correspondingClusterRole
for your application namedfoo:baz
with the namespace as a suffix to prevent overlapping with other applications.Can you accomplish the motivating task without this feature, and if so, how?
A
replacement
comes close but you would need multiple to match what the currentnameref
transformer does. For example, you not only need to edit resources names, you need to edit references on other resources, e.g. a Role'sroleRef
field using the same name.What other solutions have you considered?
N/A
Anything else we should know?
No response
Feature ownership
The text was updated successfully, but these errors were encountered: