You'd need to filter that out in your script - this is just how the changes get passed down. Generally you don't want to trigger based on changes - but instead trigger on "state".
On Mon, Oct 2, 2017 at 4:20 PM, Tobias Brunner <[email protected]> wrote: > Hi all, > > I'm testing some simple oc observe scripts and facing the following > challenge: When watching for changes to quota objects I always get two > updates, f.e. when changing a quota object: First the update for the > value I've changed, f.e. "spec.hard.cpu" and immediately after that a > second event with the corresponding update to "status.hard.cpu". How can > I filter out the second update? I'm only interested in the first change > event. > > The current commandline: "oc observe quota --all-namespaces -- ./echo.sh" > > Best, > Tobias > > > _______________________________________________ > users mailing list > [email protected] > http://lists.openshift.redhat.com/openshiftmm/listinfo/users > >
_______________________________________________ users mailing list [email protected] http://lists.openshift.redhat.com/openshiftmm/listinfo/users
