Allow ad-hoc connections on a per-operation basis
Description
Environment
None
Gerrit Reviews
None
Release Notes Description
None
Activity
Show:
Fixed
Pinned fields
Click on the next to a field label to start pinning.
Details
Details
Assignee

Reporter

Story Points
0
Sprint
None
Fix versions
Priority
Instabug
Open Instabug
PagerDuty
PagerDuty Incident
PagerDuty

PagerDuty Incident
Sentry
Linked Issues
Sentry
Linked Issues
Zendesk Support
Linked Tickets
Zendesk Support

Linked Tickets
Created November 15, 2022 at 12:52 PM
Updated December 12, 2022 at 4:23 PM
Resolved December 12, 2022 at 4:23 PM
Instabug
A new feature request that came up is that in addition to specifying the connection up front, it should be possible to provide the connection information on a per-operation basis.
The proposal is to latch this onto the new ConnectionIdentifier feature, and if it is a URI/Connection String, extract all the necessary information from there and spin up a connection. A UUID/hashCode connection identifier that is temporary can be chosen as an example.
One important property is that if the connection identifier / URI Is the same, it should be reused like the other connections and shut down when the application is terminated.