[Data Views] Align the namespace parameter with the documentation

[dokmic]

Currently, the namespace parameter in the data view create API is not taken into account. In the code, it is some sort of a read-only parameter.

We should either update the documentation or fix that in the code.

[elasticmachine]

Pinging @elastic/kibana-app-services (Team:AppServicesSv)

[tsullivan]

As a workaround, you can call the create data view API using a URL path under a space name:

curl -X POST /s/my-space-name/api/data_views/data_view
{ "data_view": {} }


But this does not give you the ability to create the data view in multiple spaces.

[AndrewMcQuerry]

Does this imply that there is no current method for being able to create or update a Data View via API and have it associated with multiple spaces?

I ask because I don't seem to be able to define namespaces when creating or updating a data_view via API.

POST kbn:/api/data_views/data_view
{
  "data_view": {
    "id": "default_index_pattern",
    "name": "default_index_pattern",
    "title": "default_index_pattern",
    "namespaces": ["default"]
  }
}

{
  "statusCode": 400,
  "error": "Bad Request",
  "message": "[request body.data_view.namespaces]: definition for this key is missing"
}

[alemansec]

indeed, as an end-user relying solely on api to deploy and configure my clusters and kibana instances, i ran into this (i submitted the issue to support.elastic.co leading to this github issue),

it also prevents me from having the same ID for data views over multiple spaces (because of the conflicting objects response), feature we were previously using with versions < 8 to edit/validate dashboards on a given space, later copying them unchanged to the spaces exposed/used by our customers.

[elasticmachine]

Pinging @elastic/kibana-data-discovery (Team:DataDiscovery)

[orsius]

Dear all, is anyone is aware of any developments on this topic?

Currently, the namespace parameter in the data view create API is not taken into account. In the code, it is some sort of a read-only parameter.

We should either update the documentation or fix that in the code.

Waiting for you feedback,
kr,

ps: I recently open a similar topics under: https://discuss.elastic.co/t/kibana-api-data-view-not-working-as-expected-with-namespaces-parameter/327168

[AndrewMcQuerry]

I'd like to bump this and reiterate that in an Enterprise environment, with many Kibana Spaces and many "standard" Data Views, it is extremely important that we have the ability to manage Data Views (and the namespace(s) they are shared with) from the Kibana API.

[davismcphee]

Just wanted to share an update that this issue has now been addressed in #155815, and the create data view API now considers the namespaces parameter as expected. While we don't have any plans to support namespaces in the update API, we already have an existing API that can do this called _update_objects_spaces. Thanks all for the input!