![]() I consider this a non-starter, as this isn't a pattern we likely want to persist in the NP. Use server.inject to mimic what's happening in option 1 above.This potentially involves changing the way that the secure SOC wrapper authorizes requests, which could prove time consuming. Expose a way to create SavedObjectsClient instances that can be bound to an arbitrary namespace.This will allow us to circumvent the scoped client, but it requires us to implement our own authz, and this endpoint won't be able to take advantage of any other SOC wrappers that may exist. Rewrite the import/export clients to optionally accept a SavedObjectsRepository instead of a SavedObjectsClient.This potentially requires the least amount of effort, however. ![]() I don't love this option as it'll potentially be memory intensive on the client, and may not scale for larger datasets.
0 Comments
Leave a Reply. |