fix: 🐛 forward secure
in StorageHelper for s3
#1205
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.
Related Issue \ discussion
After b78e9b9, secure is now default to
True
. We need to forwardsecure
key otherwise, even if it has been set toFalse
, it switches back toTrue
.Patch Description
At
clearml/clearml/storage/helper.py
Line 2069 in 0594a5a
secure
key is correctly fetched from the config file.When
self._conf.update
is called right after,secure
is automatically changed toTrue
.Testing Instructions
Install latest version of clearml (1.14.3). Try with
secure: false
inclearml.conf
underaws.s3.credentials
.You should get a similar error: