search

elastic / kibana

Your window into the Elastic Stack
https://www.elastic.co/products/kibana
Other
19.5k stars 8.05k forks source link

[Index Management] API Request Inconsistent by Clicking Around #150395

Open nicpenning opened 1 year ago

nicpenning commented 1 year ago

Kibana version: 8.6.1 Elasticsearch version: 8.6.1 Server OS version: Windows 11 Browser version: MS Edge 109.0.1518.78 Browser OS version: 64 Bit Original install method (e.g. download page, yum, from source, etc.): Download Page / On Premise / Extract -> Execute Describe the bug:

When using Index templates in Kibana you can use the Request feature to see the API POST Request, however, even if you don't make any changes to the template and simply click the Mappings page and then Advanced Options, it automatically populates additional settings.

Steps to reproduce:

  1. Create New Index Template
  2. Check POST Request
  3. Go to Mappings and click Advanced Options
  4. Go back to POST Request and see that it added more options to the POST Request

Expected behavior: What I would expect is that if no changes are made in the Advanced Options then it shouldn't alter the POST API Request.

Screenshots (if relevant): magic

Any additional context: I am trying to handle the rather daunting load of managing Index Templates for Elastic Agent migrations and to be consistent and manageable I keep all of the POST requests to rebuild these from the API if needed.

elasticmachine commented 1 year ago

Pinging @elastic/platform-deployment-management (Team:Deployment Management)

yuliacech commented 1 year ago

Related to https://github.com/elastic/kibana/issues/106151

nicpenning commented 1 month ago

FYI this still exists, even with 8.14.0. Same rules apply.

nicpenning commented 4 days ago

Please, please, please address this - This still applies to 8.14.2.

Even if you are not using the API request, we have recently noticed that when a component template was altered, these settings were applied (on the right is what clicking around in the index template management does):

image

When this occurred, it broke all of the ECS mapping because it set dynamic mapping to false and it corrupted the mapping on roll over for this datastream and not ECS fields were being dynamically mapped.