21s Normal ResourceInProgress Bundle UpdateInstanceRequestInFlight: Update request for ServiceInstance in-flight to Broker
21s Normal BundleInProgress Bundle
20s Normal ResourceInProgress Bundle UpdatingInstance: The instance is being updated asynchronously
19s Normal ResourceInProgress Bundle UpdatingInstance: The instance is being updated asynchronously (Resource is being updated)
5s Normal ResourceReady Bundle InstanceUpdatedSuccessfully: The instance was updated successfully
5s Normal ResourceReady Bundle InjectedBindResult: Injected bind result
5s Normal ResourceReady Bundle
5s Normal ResourceReady Bundle ProvisionedSuccessfully: The instance was provisioned successfully
5s Normal BundleReady Bundle
Why is this good? Because we can see stuff like this in the events now:
4s Normal ResourceInProgress Bundle UpdatingInstance: The instance is being updated asynchronously (See Micros events using 'micros stream:poll ychen-test-svc-noderefapp -e ddev -i qhlpdjse1orn3e4p')
Using another system that groups these events and resources together we can build a nicer summary of what exactly happened in the state.
Fixes #94.
Each event is annotated with the resource name:
Why is this good? Because we can see stuff like this in the events now:
Using another system that groups these events and resources together we can build a nicer summary of what exactly happened in the state.