We are currently targeting Kibana Spaces for 6.5 (elastic/kibana#18948). With this implementation, Kibana will support multi-tenancy. If we change nothing today, every user that follows the add data instructions will end up importing the module dashboards into the default space (assuming they even have access to this). As an end user, if I followed these instructions, I would expect the dashboards to be available in the space that I'm currently in.

As modules currently utilize the dashboard import/export API (elastic/kibana#10858), I want to make sure we support Spaces out of the box. This actually works today as long as the URL is formatted appropriately.

Today
API endpoint
/api/kibana/dashboards/export?dashboard=7adfa750-4c81-11e8-b3d7-01146121b73d

With Spaces
Default Space API endpoint (same as above)
/api/kibana/dashboards/export?dashboard=7adfa750-4c81-11e8-b3d7-01146121b73d

Specific Space API endpoint
/s/space-id/api/kibana/dashboards/export?dashboard=7adfa750-4c81-11e8-b3d7-01146121b73d

I've tested this with a Space ID and it does work. Are there any changes that we need to add to support this? Should we have users add the default Kibana URL and add an option to add one or multiple Spaces from CLI or the config yaml? How important is it to have a single data source (the beat) and dashboards in multiple Kibana Spaces?

We should also either intelligently add the URL / space ID to the UI tutorials or add some descriptive text around using the Space URL generically.

cc: @ruflin @tsg @legrego @kobelb @acchen97