Skip to content

docs: document applies_to authoring for settings YAML - #4047

Open
florent-leborgne wants to merge 12 commits into
mainfrom
flb/settings-yaml-applies-to
Open

docs: document applies_to authoring for settings YAML#4047
florent-leborgne wants to merge 12 commits into
mainfrom
flb/settings-yaml-applies-to

Conversation

@florent-leborgne

Copy link
Copy Markdown
Member

Why

Kibana settings YAML files treat automated_settings.md as the schema source of truth. That page previously said {settings} YAML follows the same applies_to rules as page Markdown. Authors then omitted deployment keys or copied stack: preview onto ech.

What

Documents the settings-YAML authoring contract. stack carries lifecycle and version. ech, ece, eck, self, and serverless are support flags (ga or unavailable).

For Advanced Settings that exist on only some serverless projects, nest elasticsearch, observability, security, or vectordb under serverless. Do not nest workplace_ai. Write a scalar serverless: ga or serverless: unavailable when every project matches. Do not mix a scalar serverless: with project keys.

Previous defaults go in a gated note. Use inline {applies_to} in the description for other version-scoped behavior.

The syntax example YAML now uses a complete map, including stack: preview plus ech: ga.

Supersedes #4014 (fork PR). Same-repo branch so docs preview can create a deployment.

Related: elastic/kibana#288454

Made with Cursor

florent-leborgne and others added 9 commits September 2, 2026 14:59
Settings YAML uses the same keys as body Markdown, but deployment
keys are support flags so the Supported on line stays readable.

Co-authored-by: Cursor <cursoragent@cursor.com>
Co-authored-by: natasha-moore-elastic <137783811+natasha-moore-elastic@users.noreply.github.com>
A scalar serverless flag over-claims when a setting exists on only
one serverless project. Nest elasticsearch, observability, and
security when they differ.

Co-Authored-By: Cursor Grok 4.6 <noreply@anthropic.com>
Co-authored-by: Cursor <cursoragent@cursor.com>
Advanced Settings may exist on only some serverless projects.
Nest elasticsearch, observability, or security when that is true.

Co-Authored-By: Cursor Grok 4.6 <noreply@anthropic.com>
Co-authored-by: Cursor <cursoragent@cursor.com>
Map vectordb, skip workplace_ai, and show previous defaults in a gated note instead of inline description bullets.
@github-actions

github-actions Bot commented Sep 6, 2026

Copy link
Copy Markdown

Docs preview (local build)

Handbook preview: https://docs-v3-preview.elastic.dev/elastic/docs-builder/pull/4047/

Sample changed pages:

@natasha-moore-elastic natasha-moore-elastic left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

A couple of suggestions for the examples, otherwise LGTM!

Comment thread docs/syntax/settings-with-applies-example.yml
Comment thread docs/syntax/settings-with-applies-example.yml Outdated
Comment thread docs/syntax/settings-with-applies-example.yml Outdated
Co-authored-by: natasha-moore-elastic <137783811+natasha-moore-elastic@users.noreply.github.com>
Co-authored-by: natasha-moore-elastic <137783811+natasha-moore-elastic@users.noreply.github.com>
The warning was tagged ga 9.2 on a setting that was also ga 9.2, so the gate did not filter anything.

Co-authored-by: Cursor <cursoragent@cursor.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

documentation Improvements or additions to documentation

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants