Add Views Security Model

[jfreden]

This PR wires ES|QL views into index authorization and view resolution so view expansion preserves the same security/error semantics as direct index access.

• Adds EsqlResolveViewAction plus ViewResolutionService to resolve views from project metadata using ResolvedIndexExpressions, including strict handling for unauthorized and missing concrete targets.
• Refactors ViewResolver to resolve views asynchronously, recurse through nested/wildcard view references, detect circular references/max depth, and keep unresolved non-view targets in the rewritten plan rather than dropping them.
• Updates EsqlSession to run view replacement asynchronously and carry viewQueries in Configuration, so source/view context survives later planning and serialization.
• Updates view CRUD/read request handling to resolve views via indices options (resolveViews=true) and reuse the same resolution path for GET view.
• Aligns security behavior by persisting resolved expressions for view-resolving requests and by handling view abstractions correctly in index-permission resource accounting (including selector/failure-store edge cases).

[github-actions]

ℹ️ Important: Docs version tagging

👋 Thanks for updating the docs! Just a friendly reminder that our docs are now cumulative. This means all 9.x versions are documented on the same page and published off of the main branch, instead of creating separate pages for each minor version.

We use applies_to tags to mark version-specific features and changes.

Expand for a quick overview

When to use applies_to tags:

✅ At the page level to indicate which products/deployments the content applies to (mandatory)
✅ When features change state (e.g. preview, ga) in a specific version
✅ When availability differs across deployments and environments

What NOT to do:

❌ Don't remove or replace information that applies to an older version
❌ Don't add new information that applies to a specific version without an applies_to tag
❌ Don't forget that applies_to tags can be used at the page, section, and inline level

🤔 Need help?

• Check out the cumulative docs guidelines
• Reach out in the #docs Slack channel

[github-actions]

🔍 Preview links for changed docs

• docs/reference/elasticsearch/index-lifecycle-actions/ilm-wait-for-snapshot.md
• docs/reference/enrich-processor/geoip-processor.md
• docs/reference/query-languages/esql/README.md

[n1v0lg]

This is looking good! Sorry I ran out of time for the day. I just need to wrap up reviewing ViewResolver and the tests. Doing that first thing tomorrow morning.

[n1v0lg]

Note: I'm deferring to the other reviewers here since it's ES|QL code. It looks complicated but I'm assuming there's not way around it.

[n1v0lg]

Nit: It feels off that a boolean "check" style method would trip an assertion -- maybe we can combine shouldSetResolvedIndexExpressions and actually setting the expressions into one method and call it maybeSetResolvedIndexExpressions. WDYT?

[jfreden]

I was going back and forth on this and landed on this approach with the motivation that we will eventually remove shouldSetResolvedIndexExpressions and #135799 will be fixed, and when it is, this is kind of what it would look like IMO.

[n1v0lg]

I think #135799 may stick around for some time, unfortunately. It's one of those things that isn't painful enough to get prioritized but maybe I'm overly pessimistic.

[n1v0lg]

There's an exclusion edge where this breaks I think: if do something like GET view*,-view-1,view* you should get back results for views* (because exclusions are sensitive to order). That sort of index expression is weird and I can't come up with a good reason to write it so perhaps it's okay to leave it unhandled but ideally we'd fix it somehow.

[n1v0lg]

The core logic minus exclusions LGTM. Nice test coverage, too 👍

For exclusions, see my inline comments. The main problem is that we don't preserve order and also drop the occurrence of the same pattern incorrectly which breaks some exclusion edge cases. In the interest of progress, I think it's okay to merge this PR but I do think we need exclusion handling follow ups.

[n1v0lg]

Hm it the edge case gets a little less far fetched once you write a view with an exclusion in it:

public void testViewBodyWithExclusionCombined() {
    addView("safe-logs", "FROM logs*,-logs-secret");
    addIndex("logs-public");
    addIndex("logs-secret");
    LogicalPlan plan = query("FROM safe-logs,logs-secret");
    assertThat(replaceViews(plan), matchesPlan(query("FROM logs*,-logs-secret,logs-secret")));
}

Is that I'd expect to happen. It would give us logs-secret.

Instead we get:

public void testViewBodyWithExclusionCombined() {
    addView("safe-logs", "FROM logs*,-logs-secret");
    addIndex("logs-public");
    addIndex("logs-secret");
    LogicalPlan plan = query("FROM safe-logs,logs-secret");
    assertThat(replaceViews(plan), matchesPlan(query("FROM logs-secret,logs*,-logs-secret")));
}

Meaning empty.

[n1v0lg]

FROM safe-logs,logs-secret seems like a fairly natural query to write:

Maybe I started querying safe logs FROM safe-logs and now I'm interested in both safe logs and secret logs so I write:

FROM safe-logs,logs-secret

[github-actions]

✅ Vale Linting Results

No issues found on modified lines!

---

The Vale linter checks documentation changes against the Elastic Docs style guide.

To use Vale locally or report issues, refer to Elastic style guide for Vale.

[coderabbitai]

Important

Review skipped

Auto reviews are limited based on label configuration.

🏷️ Required labels (at least one) (2)

• Team:Delivery
• Team:Search - Inference

Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

⚙️ Run configuration

Configuration used: Path: .coderabbit.yml

Review profile: CHILL

Plan: Pro

Run ID: 3889d5ce-5525-4c99-905f-7debfc641b4c

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

• 🔍 Trigger review

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}