The plain provisioner doesn't reconcile changes to a local configmap

[timflannagan]

When creating a BundleDeployment that references a local CM, and that CM has been updated, the plain provisioner doesn't appear to watch that resource. In the case that the referenced CM had invalidate data, e.g. an invalid metadata.Name, and this resulted in a failed installation, then the plain provisioner won't react to when the underlying CM has been updated.

[timflannagan]

Note: this could lead to imperative behavior where I need to delete the CM/BD and re-create them in order to get the desired behavior.

[asmacdo]

I'd like to work on this, I'll assign if I find the time.

[github-actions]

This issue has become stale because it has been open 60 days with no activity. The maintainers of this repo will remove this label during issue triage or it will be removed automatically after an update. Adding the lifecycle/frozen label will cause this issue to ignore lifecycle events.