[runtime_env] Add the ability to inject a setup hook for customization of runtime_env on init #24036
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
pcmoritz
approved these changes
Apr 20, 2022
6 tasks
pcmoritz
added a commit
that referenced
this pull request
Apr 30, 2022
This extends #24036 to also cover job submission. Co-authored-by: Eric Liang <ekhliang@gmail.com>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Why are these changes needed?
This adds an environment variable hook which can be used to arbitrarily rewrite the runtime_env option programmatically. The user specifies a module path (e.g.,
your.module.runtime_env_hook) that receives the runtime_env option from ray.init() and can rewrite it as needed.