We're thrilled to reveal the next chapter in Keboola's journey, which is continuing to harness the power of Snowflake. Building upon our recently acquired "Powered by Snowflake" status, we're now entering a new phase of innovation that will elevate your data experience.
Data flow templates have undergone significant changes to enhance their functionality and usability. As part of these improvements, we have restructured the templates based on data sources, providing you with greater flexibility and customization options.
This is a reminder that the deadline to update your whitelist for the new outbound IP addresses is approaching. It is crucial to act before June 30, 2023, to avoid any disruption to your connectivity.
The main feature we released in May was feature toggling. Also, the dbt transformation component was updated, and we added reverse DNS entries for all our IP addresses in specific stacks.
We have added a new pre-migration check for projects migrating to the new queue. It validates that your firewalls are configured correctly to allow access from the new queue's IP addresses.
Keboola CLI now supports storage operations, allowing users to manage storage buckets, tables, and files through the command-line interface. The Storage API now fully supports JSON in request bodies, deprecating the use of form-data.
There are two types of features in Keboola Connection that can change the behavior of your project or how you as a user interact with all projects: project features and user features. We are pleased to say that we have made many features available to our users and they can turn them on if required.
We are adding new outbound IP addresses for the connection.keboola.com and connection.eu-central-1.keboola.com stacks for Queue V2.
After spending a long time testing it, we have decided to enable read-only access to Storage to all existing projects with the Snowflake backend.
When using form-data in an API request, you are limited to simple key-value pairs. However, this limitation can now be overcome by using JSON instead.