Import and export uptime-dynamic-settings using saved-object management

[kobelb]

End-users will commonly use saved-object management's import/export functionality to move saved-objects from one instance to another. The uptime-dynamic-settings saved-object should be included in these exports, so end-users have an easy way to migrate all of their saved-objects in a unified manner.

As part of the effort to remove legacy multi-tenancy, we want to give our users a way to migrate from a legacy tenant to Spaces. Without the ability to import/export the uptime-dynamic-settings saved-object, if a user is using a legacy tenant, their data will be stuck in that tenant and they won't have a migration path for 8.0.

As far as I'm aware, this shouldn't be blocked by anything 🎉 !!

[elasticmachine]

Pinging @elastic/uptime (Team:uptime)

[andrewvc]

@kobelb is there an action item for us here?

[kobelb]

Hey @andrewvc, yup :) Prior to 8.0, we'll want to make the uptime-dynamic-settings saved-object exportable/importable. #82784 has an example of how to do so.

[dominiqueclarke]

@shahzad31 I am not able to inspect the save object, but I am able to download/export it. Is this expected?

[shahzad31]

@dominiqueclarke yes that's expected behaviour we can't inspect these objects.

[dominiqueclarke]

Post FF testing LGTM