Azure / eno

Language-agnostic configuration management for Kubernetes
MIT License
7 stars 5 forks source link

Avoid unnecessary resynthesis when using revision annotations #209

Closed jveski closed 1 month ago

jveski commented 1 month ago

Currently the revision annotations only block synthesis until all inputs match. Once they match, any change to the resource version will result in resynthesis.

Intuitively, I expect the revision annotation to take precedence over the resource version. Meaning that the input is not considered to have changed unless the revision is modified. I suspect others will assume the same.

This has a nice side effect: revisions can be used to filter out input status updates which are unlikely to result in meaningful resynthesis.