Data Orchestration 24.12
New Storage View with Folder Navigation - Beta
We've introduced a completely redesigned storage details view in the storage section. This dedicated view enables real-time navigation through files and folders, providing a more intuitive way to browse your storage contents.
Custom Price Book GraphQL APIs
- Introduced new APIs for complete price book management:
- Create, update, list, and delete custom price books
- Attach custom price books to storage locations
Users and Role Management
- Enhanced Role Configuration UI: Client option is now removed, and you can now edit a role by members or managers. A client or a user can be added as a member or a manager.
- API Client Role Management : API clients can now act as role managers, allowing programmatic control over role permissions through API calls. To enable this feature, a new "Managers" option is available in the role edit panel when configuring API clients.
- User Management Webhooks: New webhook events have been added for user lifecycle management, specifically for user creation and deletion. These webhooks enable automated user management workflows.
New S3 Storage Validation
Added a 'size' validation strategy for S3 (and S3-compatible) storage types so only the size of the object is checked after uploading. This not a validation strategy we generally recommend, but it is useful when working around bugs in some S3-compatible storage implementations.
Microsoft Entra ID Integration and Role Synchronization
CloudSoda now supports seamless integration with Microsoft Entra ID (formerly Azure AD) for enhanced role management. This feature enables:
- Synchronization of Microsoft Entra ID Groups with CloudSoda roles
- Direct management of user permissions from the Microsoft Entra ID console
- Automated role assignment based on your Entra ID group configurations
To get started read the following documentation on How Sync Azure Entra ID Groups with CloudSoda Roles
Deprecation Notice: Legacy Field Removal
We have completed the removal of previously deprecated fields (announced for removal no earlier than December 1, 2024). This cleanup ensures API consistency and prevents new integrations from being built on outdated fields. If you haven't updated your integration to use the current field structure, please review our API documentation for the latest field specifications.
Comments
0 comments
Article is closed for comments.