Octue

Latest version: v0.61.0

Safety actively analyzes 688823 Python packages for vulnerabilities to keep your Python projects secure.

Scan your dependencies

Page 16 of 40

0.23.4

Not secure
Summary
Remove the need for alternative constructors when instantiating datafiles from the cloud or from a local directory - the `Dataset` constructor now handles this automatically.

<!--- SKIP AUTOGENERATED NOTES --->
Contents ([445](https://github.com/octue/octue-sdk-python/pull/445))

Enhancements
- Unify local and cloud dataset instantiation via `Datafile.__init__`
- Raise a deprecation warning if datasets are constructed via `Dataset.from_cloud` or `Dataset.from_local_directory`

<!--- END AUTOGENERATED NOTES --->

0.23.3

Not secure
Summary
Add a single method for updating stored datafile and dataset metadata that deduces whether to update the local or cloud metadata.

<!--- SKIP AUTOGENERATED NOTES --->
Contents ([443](https://github.com/octue/octue-sdk-python/pull/443))

Enhancements
- Add `Datafile.update_metadata` method
- Add `Dataset.update_metadata` method

Refactoring
- Rename `update_cloud_metadata` parameter to `update_metadata` in `Datafile` instantiation and raise a deprecation warning if the old parameter name is used

<!--- END AUTOGENERATED NOTES --->

0.23.2

Not secure
<!--- SKIP AUTOGENERATED NOTES --->
Contents ([440](https://github.com/octue/octue-sdk-python/pull/440))

Enhancements
- Add ability to download datafiles from a signed URL without cloud permissions
- Add `Datafile.generate_signed_url` method
- Raise error if trying to modify a URL-based datafile
- Raise error if trying to generate a signed URL for a local datafile or dataset

Refactoring
- Use URI terminology in cloud storage path module

Testing
- Test that datafiles and datasets can be downloaded from URLs without cloud permissions

<!--- END AUTOGENERATED NOTES --->

0.23.1

Not secure
Summary

<!--- SKIP AUTOGENERATED NOTES --->
Contents ([439](https://github.com/octue/octue-sdk-python/pull/439))

Enhancements
- Validate output locations given to `Runner`

Dependencies
- Use `twined=^0.4.1`

<!--- END AUTOGENERATED NOTES --->

0.23.0

Not secure
Summary
This release provides public methods and a context manager for updating datasets' metadata easily. It also standardises the internals of metadata getting, setting, and using across `Datafile` and `Dataset`.

<!--- SKIP AUTOGENERATED NOTES --->
Contents ([436](https://github.com/octue/octue-sdk-python/pull/436))

New features
- Add context manager for updating dataset stored metadata

Enhancements
- Add new `Metadata` mixin to `Datafile`, `Dataset`, and `Manifest`
- Allow kwargs to be provided to `Dataset.from_cloud`

Fixes
- Stop creating local metadata file on instantiation of `Dataset`
- Stop implicitly uploading metadata when calling `Dataset.from_cloud`
- Add missing `name` property setter to `Dataset`
- Use correct metadata path for signed URL datasets

Refactoring
- Factor out `metadata` method into new `Metadata` mixin
- Rename `Dataset._upload_cloud_metadata` to `Dataset.update_cloud_metadata`
- Rename `Dataset._save_local_metadata` to `Dataset.update_local_metadata`

<!--- END AUTOGENERATED NOTES --->

0.22.1

Not secure
Summary
This release simplifies the `Datafile` class internals and clarifies its metadata resolution order. Stored metadata will now be used in preference to instantiation metadata unless the `hypothetical` parameter is `True`, allowing the removal of some confusing internal logic from the class.

<!--- SKIP AUTOGENERATED NOTES --->
Contents ([433](https://github.com/octue/octue-sdk-python/pull/433))

Enhancements
- If `hypothetical` is not `True` when re-instantiating existing datafiles, always use their stored metadata (from the cloud object or local metadata file)
- Store cloud metadata on `Datafile` instances without the `octue__` namespace prefix in its keys
- Make `Datafile` metadata update methods public so they can be called easily by users
- Make it optional whether to include the SDK version in the output of `Datafile.metadata`
- Return `None` from `GoogleCloudStorageClient.get_metadata` if bucket not found instead of raising an error

Fixes
- Allow instantiation of a cloud datafile with a non-existent or inaccessible cloud path (defer raising errors until attempting to access it)

Refactoring
- Simplify `Datafile` internals by removing the "initialisation parameters" concept
- Rename `Datafile._get_local_metadata` to `Datafile._use_local_metadata`
- Align `Datafile._use_cloud_metadata` and `Datafile._use_local_metadata` methods
- Factor out setting `Datafile` instance metadata from stored metadata into `_set_metadata` method

<!--- END AUTOGENERATED NOTES --->

Page 16 of 40

Links

Releases

Has known vulnerabilities

© 2024 Safety CLI Cybersecurity Inc. All Rights Reserved.