You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Seems that managed fields are killing the concept of katafygio.
I didn't looked for my katafygio repo for a while because it was working quite good but i recently discovered that there was a lots of commits in the repo. The main reason seems to be there is a lot of changes in annotations
Some exemples:
I can think about one way to solve that kind of issues with a generic approach by allowing filtering out some jsponpath address or similar .metatda.annotations that won't count into the diff comparison
what do you think ?
The text was updated successfully, but these errors were encountered:
Changes in your example all come from managedFields which indeed are irrelevant and noisy. Those are filtered out in recent releases, can you try an upgrade?
Other than that, annotations shouldn't be noisier than an other field. Generically stripping chosen fields might be possible yes, though could cause bad surprises when defined cluster wide, unless expressed as per object, or kind, or namespace (which becomes more involved). Whenever possible I'd like to fix pathological cases (like managedFields were).
Seems that managed fields are killing the concept of katafygio.
I didn't looked for my katafygio repo for a while because it was working quite good but i recently discovered that there was a lots of commits in the repo. The main reason seems to be there is a lot of changes in annotations
Some exemples:
I can think about one way to solve that kind of issues with a generic approach by allowing filtering out some jsponpath address or similar
.metatda.annotations
that won't count into the diff comparisonwhat do you think ?
The text was updated successfully, but these errors were encountered: