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 two new resources under the /storage/v1/diag path which are provided by the StatusStorageResource and TreeStorageResource implementations make strong assumptions about the storage system in use since they only use the folderPath of the configured filesystem. Before the introduction of these resources it was quite easy to add support for other storage options (S3 for example).
Would it be possibly to provide an abstraction that might be used by the resources under /storage/v1/diag to allow other storage options? I was thinking about something like a DiagnosticService interface which could be implemented for other storage options.
Cheers
The text was updated successfully, but these errors were encountered:
Before we introduce an interface refactor it is possible to just NOP the two diagnostics resources StatusStorageResource.java can return only the collectMachineInfo part and TreeStorageResource.java can just return an empty string "".
The two new resources under the
/storage/v1/diag
path which are provided by theStatusStorageResource
andTreeStorageResource
implementations make strong assumptions about the storage system in use since they only use thefolderPath
of the configured filesystem. Before the introduction of these resources it was quite easy to add support for other storage options (S3 for example).Would it be possibly to provide an abstraction that might be used by the resources under
/storage/v1/diag
to allow other storage options? I was thinking about something like aDiagnosticService
interface which could be implemented for other storage options.Cheers
The text was updated successfully, but these errors were encountered: