Pull secrets from environment when running locally #2800
+61
−5
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 the changes needed?
When running locally, it is not natural to have a
_FSEC_
prefix on your secrets.What changes were proposed in this pull request?
With this PR, the
_FSPEC_
prefix is not used anymore for local execution.How was this patch tested?
I added unit tests to this PR to check the new behavior and ran this test:
export MYGROUP_APIKEY=my-secret pyflyte run --remote main.py check_secret
Setup process
Screenshots
Check all the applicable boxes