Descarteslabs

General

- Updated copyright message everywhere.

Auth

- To prepare for multi-audience support in the clients, support for new custom claims in tokens has been added so that the user's unique namespace, which serves as a global id for the user, can be determined without resort to computing it on the fly.

Catalog

- Fixed a bug where some geometries weren't supported by blob geometry properties.

Vector

- *Breaking change* in the past, regardless of the ordering of columns when a `Table` was created, or the ordering of columns in the `TableOptions`, the result of a feature query would always place the `uuid` column last. As of this version, the behavior has been modified to preserve the ordering of columns, so that if no column list is provided in the options, the `uuid` column will appear in the position it has in the underlying table, as per the `Table.columns` property. Similarly if a query specifies an explicit list of columns in the `TableOptions`, `uuid` will appear in the same position in the result as it does in the supplied list of columns. However in keeping with prior behavior, if an explicit list of columns does not include `uuid`, it will always be added automatically at the end and will appear in the last column of the result.
- The `ilike` `property_filtering` expression type has been added to support case-insensitive wildcard matching of Vector Table column values.

Catalog

- Fixed a problem with unpickling Catalog objects pickled with an earlier version. Please be aware that we do not support the pickling of any Catalog objects, so if in doubt, don't do it!

Authentication

- The links for interacting with login and token generation have been updated to refer to `https://app.descarteslabs.com`.

Catalog

- All `CatalogObject` classes which support the `owners`, `writers`, and `readers` fields have been refactored to derive this support from the new `AuthCatalogObject`. This change does not affect the behavior of any of these classes. The methods `AuthCatalogObject.user_is_owner()`, `AuthCatalogObject.user_can_write()`, and `AuthCatalogObject.user_can_read()` have been added to allow testing of permissions prior to attempting an operation such as updating or deleting the object.
- `EventSchedule` now has a read-only `expires` attribute which indicates when the schedule will be expired and deleted.
- `EventSubscription` now has a read-only `owner_role_arn` field which contains the AWS Role which will be used by certain `EventRule` targets that reside in an external AWS account.
- `EventRule` has been enhanced to support SQS Queue targets.
- Several new helper classes for use with `EventSubscription` are now supported: `EventSubscriptionSqsTarget`, `NewImageEventSubscription`, `NewStorageEventSubscription`, `NewVectorEventSubscription`, and `ComputeFunctionCompletedEventSubscription`. The latter supports events generated by the Compute service as described below.

Compute

- The Compute service now generates a `compute-function-completed` event every time the number of outstanding (pending or running) jobs transitions to 0, akin to the `Function.wait_for_completion()` method. These can be used with the Catalog service events support to trigger other operations.

General

- Support for Python 3.8 has been removed
- Support for Python 3.12 has been added
- Some dependencies have been updated due to security flaws
- The dependency on `pytz` has been removed in favor of the standard `zoneinfo` package
- Minor changes and additions to the client exception hierarchy so that ClientErrors and ServerErrors are not conflated in the retry support.

Catalog

- The Catalog now provides support for Events, essentially notifications of new or updated assets in the Catalog, including images and storage blobs. Additionally, scheduled calendar-based events can be defined. You can subscribe to these events to trigger running a Compute function of your choice. This makes it possible to set up automated processing of new imagery. See the [https://docs.descarteslabs.com/guides/catalog.html](Catalog Guide) and API documentation for more information.

General

- Due to declining support for Python 3.8 across the ecosystem, we have discontinued our support for Python 3.8. It is expected that the client will continue to function until Python 3.8 is End of Life (October 2024), but we can no longer test new releases against this version.

Catalog

- The Catalog Storage Blob deletion methods have been enhanced to support waiting for completion of the operation. When a blob is deleted, it is removed immediately from the catalog and a background asynchronous task is launched to clean up the contents of the blob from the backing storage. If a blob is deleted and then a new blob with the identical id is immediately created and uploaded before this background task completes, it is possible for the background task to end up deleting the new blob contents. As of this release the `Blob` instance and class delete methods return a `BlobDeletionTaskStatus` object which provides a `wait_for_completion` method which can be used to wait until the background task completes and it is safe to create a new blob with the same id. For the `Blob.delete_many` method, the `wait_for_completion=True` parameter can be used to wait for all the supplied blobs to be completely deleted. Note that in the case of the `Blob.delete` class method, this is a very slight breaking change, as it used to return True or False, and now instead returns a `BlobDeletionTaskStatus` or `None`, which have the same truthiness and hence are very likely to behave identically in practical use.

Bugfix only

General

- The `descarteslabs` client CLI script generated by the installation process was broken. Now it works!