-
Notifications
You must be signed in to change notification settings - Fork 25.2k
Remove SecurityManager policy classes #127653
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
Now that SecurityManager is no longer used, we can remove the Elasticsearch policy classes and helpers.
Pinging @elastic/es-core-infra (Team:Core/Infra) |
@@ -88,40 +86,6 @@ public class BootstrapForTesting { | |||
IfConfig.logIfNecessary(); | |||
} | |||
|
|||
static Map<String, URL> getCodebases() { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'm not super familiar but is the "init the priviledged operation" code above still relevant w/o security manager?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I will remove that in a followup, it hits several tests.
💚 Backport successful
|
Now that SecurityManager is no longer used, we can remove the Elasticsearch policy classes and helpers.
Now that SecurityManager is no longer used, we can remove the Elasticsearch policy classes and helpers.