If you delete an index template that's in use by a data stream, you'll get back lots of error details but they aren't surfaced in the UI. Ideally you should be able to click a button in the error toast to get more info.
{
"templatesDeleted": [
"special%"
],
"errors": [
{
"name": "special",
"error": {
"status": 400,
"payload": {
"message": "unable to remove composable templates [special] as they are in use by a data streams [special%]",
"attributes": {
"error": {
"root_cause": [
{
"type": "illegal_argument_exception",
"reason": "unable to remove composable templates [special] as they are in use by a data streams [special%]"
}
],
"type": "illegal_argument_exception",
"reason": "unable to remove composable templates [special] as they are in use by a data streams [special%]"
}
}
},
"options": {
"statusCode": 400,
"body": {
"message": "unable to remove composable templates [special] as they are in use by a data streams [special%]",
"attributes": {
"error": {
"root_cause": [
{
"type": "illegal_argument_exception",
"reason": "unable to remove composable templates [special] as they are in use by a data streams [special%]"
}
],
"type": "illegal_argument_exception",
"reason": "unable to remove composable templates [special] as they are in use by a data streams [special%]"
}
}
}
}
}
}
]
}
Deleting component templates
Similarly, if you delete component templates that no longer exist, you'll get back lots of error details but they aren't surfaced in the UI. Ideally you should be able to click a button in the error toast to get more info.
Deleting index templates
If you delete an index template that's in use by a data stream, you'll get back lots of error details but they aren't surfaced in the UI. Ideally you should be able to click a button in the error toast to get more info.
Deleting component templates
Similarly, if you delete component templates that no longer exist, you'll get back lots of error details but they aren't surfaced in the UI. Ideally you should be able to click a button in the error toast to get more info.