Open
Conversation
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Hi,
I was wandering is there some approach or a way to use environ in GraalVM compiled native images?
I've been trying to compile native image with current version of envrion and i get wrong or undefined values. I'm guessing that it is about compilation itself, since environ.core/env is defined with defonce and this is something that can't be changed through current functions in environ.core
Would you consider exposing read-runtime-env function that alters-var-root of environ.core/env?
This function can be called in -main function before any of env values are accessed in application code? Since change doesn't affect current flow it is somewhat reasonable request :)
Happy to hear you feedback