The package setters2 has been removed from kustomize:
https://github.com/kubernetes-sigs/kustomize/pull/5291
This commit removes the need to import setters2, by reproducing the
last link with that code, which is a minor parsing helper.
I have not changed the comment explaining what was changed from the
original, since it's still accurate. The parsing func is a buried
detail.
Signed-off-by: Michael Bridgen <mikeb@squaremobius.net>
This commit finesses the use of the debug log a little, and introduces
a trace log. The trace log gets threaded through calls to utility
procedures -- it's a little awkward putting loggers into func
parameters and structs, but it always is.
Signed-off-by: Michael Bridgen <michael@weave.works>
The update procedure is obliged to return a Result struct with all the
objects that were changed, for filling in the commit template. At
present, the result is collated by running each setter on each object
and seeing if the setter is used. This uses the `Set` from kyaml, with
a small amount of glue.
It doesn't quite work, however, because a setter may be used for a
field without changing the value. The result gets an entry for each
policy _mentioned_, whether or not it had a new value. There is no way
to see whether a setter actually changed a field from the outside,
other than by comparing a copy of the object before using the setter
with the object after (which yaml.v3 does not make easy).
A better approach is to get the setter to record whether it changed
anything, since it is there doing the changing. This means
reimplementing kyaml's `Set`. I have stripped it down to the parts
needed for image updates -- so e.g., only field values are examined.
Signed-off-by: Michael Bridgen <michael@weave.works>
Michael Bridgen
Aurel Canciu
Michael Bridgen