We want to be able to automate Elastic/Kibana provisioning as much as possible which includes Kibana roles and spaces. We use Ansible for provisioning and provisioning Elasticsearch is straightforward, however, we're struggling when it comes to Kibana.
I've used to following for creating new space(s) which works as advertised:
I get a '401' (Not authorized) error although I use the HTTP 'DELETE' verb and provide the correct space name in the url which, in turn, results in an ugly '409' status later when I want to create the space (see above).
I know I may use DELETE kbn:/api/spaces/space/<space> from within the Kibana dev tools but it doesn't help in situations when you want to automate artefact creations outside of the Kibana-environment. Is the current situation such as there's an "internal endpoint" addressable with 'kbn' but the same ReST endpoint is not exposed externally on, say, 5601?
In all of the samples given I authenticate using a "superuser" with at least kibana_admin privileges!
I feel a little lost and if anybody could point me in the right direction I'd be very grateful.
The key point here is that I removed everything certificate related and replaced them with force_basic_auth: true and status_code: 204 and they made the trick.
Apache, Apache Lucene, Apache Hadoop, Hadoop, HDFS and the yellow elephant
logo are trademarks of the
Apache Software Foundation
in the United States and/or other countries.