unsafe_load secrets.yml with psych 4 #42687
Merged
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.
Summary
Pysch 4 now defaults
YAML.load
toYAML.safe_load
, which does not allow aliases unless an aliases flag is given:ruby/psych#487
https://github.com/ruby/psych/blob/216f94fb9aacb0754f1dd2257b8d6a61b278a8b2/lib/psych.rb#L322
This PR switches secret loading to use
unsafe_load
. This should be fine becausesecrets.yml
is in-repo, and therefore trusted. I have copied the implementation from #42257, which did the same thing fordatabase.yml
This maintains backwards compatibility to allow developers to have a
secrets.yml
likeOther Information