You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The endpoint PATCH /api/v1/targets/:connectUrl/recordingOptions is an oddball and doesn't make much sense in the API, and hasn't since at least Cryostat 2.0. Perhaps it should simply be removed, or else it should be patched up to make sense and apply its settings only to the selected target. If that route is chosen, should those settings be persisted or simply held in server memory for the lifecycle of the server?
Expected Behavior
No response
Steps To Reproduce
No response
Environment
No response
Anything else?
No response
The text was updated successfully, but these errors were encountered:
Current Behavior
The endpoint
PATCH /api/v1/targets/:connectUrl/recordingOptions
is an oddball and doesn't make much sense in the API, and hasn't since at least Cryostat 2.0. Perhaps it should simply be removed, or else it should be patched up to make sense and apply its settings only to the selected target. If that route is chosen, should those settings be persisted or simply held in server memory for the lifecycle of the server?Expected Behavior
No response
Steps To Reproduce
No response
Environment
No response
Anything else?
No response
The text was updated successfully, but these errors were encountered: