I currently use the legacy IndexTemplates with the "inheritance" mechanism.
During runtime, my application, will read in plain JSON templates from the filesystem and make PutIndexTemplateRequests out of the content using the standard "source(Map<String, Object>)" API available in all Request subclasses to fill the request with the relevant content.

Now, that those templates are becoming legacy

英雄招募

成为 Doocs 项目维护者

本项目 advanced-java，包括 Doocs 开源组织下的所有项目，都欢迎各位朋友参与完善。

如果你提交的内容有价值，且具备规范性，将有机会提升为项目的维护者，直接参与项目的 review、merge 等维护工作，提交内容时也可以直接 push 到 doocs/advanced-java 主分支 master 下，无须提交 PR 等待 review。

目前 advanced-java 只有 [yanglbme](http

Kibana version:
7.9.0

Elasticsearch version:
7.9.0

Original install method (e.g. download page, yum, from source, etc.):
Pull of docker image from hub.docker.com

Describe the bug:
PR #68108 added the new setting xpack.security.sameSiteCookies, but this variable was not added to the list of known settings in the Docker startup file [kibana-docker](https://github.com/e

Related Issues

closes #4763

Short Description and Why It's Useful

You can now pass custom GraphQL query and variables to get some data.

Screenshots of Visual Changes before/after (if There Are Any)

🐛 Bug Report

This is the definition on Connection.d.ts:

interface RequestOptions extends http.ClientRequestArgs {
  asStream?: boolean;
  body?: string | Buffer | ReadableStream;
  querystring?: string;
}

To Reproduce

I've been using this class to provide authenticated connection with AWS Elasticsearch:

import { Readable } from 'stream'