Order of kubectl delete/create with kustomize configmapgenerator

[gburton1]

When you use a configmapgenerator, each config map gets a random suffix based on the content. When combined with Replace=True on the Argo Application, every change to a config map's content changes the config map's name and causes the old configmap to be deleted and the new configmap to be created. This is good because I have a watcher on these create/delete events that performs actions when they happen. The problem is that the order is not deterministic. The deletion and creation happen within milliseconds of each other. Sometimes the old config map gets deleted after the new one is created, which causes problems for my listeners on these events. Is there a way to make the order deterministic, i.e. make the deletions happen before the creations?