You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
But, as this would be a breaking change, we offer the users an opt-in mechanism for per-policy behavior. See this PR for screenshots and video, or the design itself
this also means that Endpoint exceptions become space aware. (note, here we state it's global only)
import-export: as before, they can be imported/exported, but this is still under design
We're developing this continuously behind a feature flag.
serverless: As soon as the feature is ready, we're planning to enable the feature flag and release it to serverless. Probably not much earlier as 9.3 feature freeze.
ESS: We're targeting 9.39.4 on ESS.
Resources
Here's the collection issue containing all implementation issues:
Description
We're implementing multiple changes on Endpoint exceptions:
moving to a new location
per-policy assignment[^1]: similarly to other artifacts, Endpoint exceptions can be assigned globally or per-policy.
import-export: as before, they can be imported/exported,
but this is still under designPlanned release
We're developing this continuously behind a feature flag.
Probably not much earlier as9.3feature freeze.9.39.4on ESS.Resources
Here's the collection issue containing all implementation issues:
Here's a related doc issue, that change will be released together with the changes in this issue:
Which documentation set does this change impact?
Elastic On-Prem and Cloud (all)
Feature differences
identical everywhere
What release is this request related to?
9.4
Serverless release
Around 9.3 release, maybe a bit earlier.Probably as soon as it's ready, sometime in January - will define later.
Collaboration model
The documentation team
Point of contact.
Main contact: @gergoabraham
Stakeholders: @dasansol92 @roxana-gheorghe