REX core tries to register task launchers too early
This is fine in deployments where smart_proxy_dynflow_core runs as a standalone service, because the launcher registry is always loaded before rex core. In all-in-one deployment, there is no guarantee about smart_proxy_dynflow_core being loaded before rex core and may lead to task launcher not being registered in the registry
#4 Updated by Anonymous over 1 year ago
- Status changed from Ready For Testing to Closed
Applied in changeset foreman_plugin|a37de8812199c9bd2f44082ffd87ac1e63c5efe4.