When migrating applications from one instance of EnMasse to another, or from one messaging tenant to another, it would be useful to have applications receive redirects with the new endpoints that should be used.
Design
The address specification would need to have additional fields to configure the desired redirect URLs. Likewise for messagingtenants or messagingendpoints in the shared-infra world.
In the implementation, we would need:
A feature enhancement in the router to specify an address to use redirects
A feature enhancement in the router to specify redirects for a given user (possible as part of auth plugin)
@lulf I opened a issue into JIR Qpid dispatch router DISPATCH-1632 don't know if it'is was the right place and if i putted the right description but is linked to the above issue.
Overview
When migrating applications from one instance of EnMasse to another, or from one messaging tenant to another, it would be useful to have applications receive redirects with the new endpoints that should be used.
Design
The address specification would need to have additional fields to configure the desired redirect URLs. Likewise for messagingtenants or messagingendpoints in the shared-infra world.
In the implementation, we would need:
Tasklist
TBD