From 0ab3a21a1743766d63127dae1153da626bb953af Mon Sep 17 00:00:00 2001 From: Ankit Sethi Date: Tue, 24 Jun 2025 10:30:23 -0500 Subject: [PATCH] fix file name (#129883) * fix file name * Update docs/changelog/129883.yaml * Delete docs/changelog/129883.yaml --- libs/entitlement/README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/libs/entitlement/README.md b/libs/entitlement/README.md index 261c95eb3f6be..2f25a04f5064c 100644 --- a/libs/entitlement/README.md +++ b/libs/entitlement/README.md @@ -35,7 +35,7 @@ NotEntitledException: component [(server)], module [org.apache.lucene.misc], cla ### How to add an Elasticsearch module/plugin policy -A policy is defined in an `entitlements-policy.yaml` file within an Elasticsearch module/plugin under `src/main/plugin-metadata`. Policy files contain lists of entitlements that should be allowed, grouped by Java module name, which acts as the policy scope. For example, the `transport-netty4` Elasticsearch module's policy file contains an entitlement to accept `inbound_network` connections, limited to the `io.netty.transport` and `io.netty.common` Java modules. +A policy is defined in an `entitlement-policy.yaml` file within an Elasticsearch module/plugin under `src/main/plugin-metadata`. Policy files contain lists of entitlements that should be allowed, grouped by Java module name, which acts as the policy scope. For example, the `transport-netty4` Elasticsearch module's policy file contains an entitlement to accept `inbound_network` connections, limited to the `io.netty.transport` and `io.netty.common` Java modules. Elasticsearch modules/plugins that are not yet modularized (i.e. do not have `module-info.java`) will need to use single `ALL-UNNAMED` scope. For example, the `reindex` Elasticsearch module's policy file contains a single `ALL-UNNAMED` scope, with an entitlement to perform `outbound_network`; all code in `reindex` will be able to connect to the network. It is not possible to use the `ALL-UNNAMED` scope for modularized modules/plugins.