[SavedObjectTagging] Expose flyout to assign tags to a SO

[sebelga]

As part of the UX enhancement of the <TableListView /> we want to allow the user to select one or multiple saved object and assign tags to them in bulk.

This is the design proposal for the tag assignment

Feature request

Ideally we would have a package exposing the above flyout to assign tags to one or multiple saved objects passed to it. The package would expose a KibanaProvider to pass the stateful dependencies (like the savedObjectsTagging plugin).

Note:

The current tag assignment in the tag management app has the opposite behaviour: select one or multiple tags ---> assign saved objects to them.

[elasticmachine]

Pinging @elastic/kibana-core (Team:Core)

[pgayvallet]

As discussed on slack:

Note: The current tag assignment in the tag management app has the opposite behaviour: select one or multiple tags ---> assign saved objects to them.

Yea, the assignment works the other way atm. We would need to develop a new flyout to handle the other scenario (selecting objects -> assign tags). FWIW this was initially planned to be developed for the SO management section, but we eventually abandoned the idea.

Unless I missed something, nothing is really blocking technically regarding the actual flyout implementation.

Now, regarding how this feature should be accessible / usage from elsewhere than the SO tagging management section:

The options would be:

1. Expose a function returning the connected (smart) component from the savedObjectsTagging (+OSS counterpart) API directly. (or a function just opening the flyout directly, as getAssignFlyoutOpener does)

kibana/x-pack/plugins/saved_objects_tagging/public/components/assign_flyout/open_assign_flyout.tsx

Lines 42 to 50 in 3730dd0

	export const getAssignFlyoutOpener =
	({
	overlays,
	notifications,
	theme,
	tagCache,
	assignmentService,
	assignableTypes,
	}: GetAssignFlyoutOpenerOptions): AssignFlyoutOpener =>

2. Expose the stateless component from a new package, and have the consumer manually hydrate it with the appropriate context, by having a dependency on the savedObjectTagging (or OSS) plugin to retrieve the assignment service and other mandatory dependencies.

Notes:

• both options means a dependency from any plugin needing to display this flyout against savedObjectTagging (or savedObjectTaggingOss)
• due to the IOC pattern we're using between savedObjectsTagging and savedObjectsTaggingOss, the OSS counterpart don't have many dependencies:

kibana/src/plugins/saved_objects_tagging_oss/kibana.json

Lines 10 to 11 in 5d9b9a1

	"requiredPlugins": [],
	"optionalPlugins": ["savedObjects"]

So having to depend on this plugin from anywhere else in Kibana seems fairly acceptable.

Given that, I would personally go with option 1., as it seems like the better developer experience. But I'm of course open to discussion on that.