Additional research to determine how to force the config endpoint to wait until all the OSGi component lifecycle changes related to the configuration change. The current waitForCompletion implementation only waits for the configured component to complete its lifecycle and callers may be able to hit an endpoint that is not yet present after making their change.
Potential topics include:
- OSGi bytecode weaving to add additional functionality to read component config
- Bind plugin code to add a marker interface to IDM components so we can track all the things
- Some other unknown-to-us-yet method of lifecycle management