Breaking Changes

• Filter indirection format change
  To list Cloudomation records using a filter for attributes in related records a more verbose format must be used. Existing filter queries to the Cloudomation API which use indirection must be migrated to the new schema.
  Ref: #2vy9pbt
• Modifying authentication-related fields of webhooks require re-authentication of the user
  A user needs to re-authenticate when enabling/disabling a webhook, changing the key of a webhook or configuring the webhook to require/not-require a Cloudomation login. There are dedicated REST-API endpoints to modify the `is_enabled`, `key`, and `require_login` fields. These fields cannot be changed directly by mutating the webhook record.
  Ref: #2x0m3gn
• Flow-API command `log` writes to execution log
  Previously the `log` command was writing to the execution output_value. To write to the output_value please use `set_output` or `save(output_value=…)` instead.
  Ref: #861m4cud1
• Connection execution logging moved from execution outputs to execution log
  Previously the output of connection executions would contain a “log” field. Now the logs are written to the execution logs.
  Ref: #861m4dmdk
• Simpler input_value for webhook executions
  Executions which are created as a result of a webhook call will not receive the deprecated inputs `data_json`, `data_query` and `data_cookies` any more. They were replaced by `json`, `query` and `cookies` respectively.
  Ref: #26py0xj
• Frontend routes specify the lookup field
  Links to Cloudomation records use the format `<Cloudomation host>/<record type>?id=<record id>`. Deprecated routes in the form `<Cloudomation host>/<record type>/<record id>` work until version 8.
  Ref: #2z5bwbv
• Executions started by webhooks will always inherit roles from the webhook itself
  Previously, webhooks which were configured to require a Cloudomation login would create executions which inherit roles from the user who called the webhook.
  Ref: #861m867pu
• Executions only keep the latest savepoint per default
  Added a new workspace configuration option `SAVEPOINT_RETENTION` to configure when savepoints are removed. Per default only the last savepoint will be kept.
  Ref: #85zrgj6tw

New Features

• Dependency visualisation
  The execution screen now features a live-updating visualisation of dependencies
  Ref: #2ajerh6

• Bundle manager
  We’ve made it easier to load example content in the form of bundles into your Cloudomation workspace
  Ref: #2517y0k

• Central logging
  Logging of various components were unified into a central Workspace logging feature
  Ref: #237t78t

• New example wrapper: timeout
  The timeout wrapper starts a child execution and waits for it to end within a timeout. If the timeout is exceeded, the child execution and all descendants are cancelled.
  Ref: #2vrrk47
• New example wrapper: rollback
  The rollback wrapper monitors a child execution and triggers a rollback if an error occurs.
  Ref: #2hr8kj5
• New example wrapper: validate
  The validate wrapper checks if the inputs or outputs of an execution match a defined schema. The validate wrapper can also dynamically learn from inputs and outputs and adapt the schema accordingly.
  Ref: #2g4v31m
• Default roles bundle
  As an example of various roles and permission sets we provide a “Default roles” bundle.
  Ref: #275xk18
• Allow to specify encoding of SSH connector outputs
  The SSH connector can be configured to parse output in encodings other than utf-8.
  Ref: #2zb2zex
• New connector type MSTEAMS
  Create connector cards in MS teams.
  Ref: #2y8vb90
• New connector type WEBDAV
  Access WebDAV services.
  Ref: #2yzkcmh
• Helper to run batch scripts for PS connector
  Run a batch script specified as a string.
  Ref: #31ng5tt
• Webhook calls redirect to login page when `require_login` is used and no valid session exists
  If a webhook is configured to require a Cloudomation login session and none exists, the webhook will return a redirect to the login screen. After successful authentication the user will be redirected back to the webhook.
  Ref: #861m8j4wm

• Possibility to specify non-standard port for REST connector in individual mode
  Previously only in URL mode a non-standard port could be specified.
  Ref: #2u591p4
• Method to import resources via Flow-API
  Add a method to the Flow-API to allow the import of exported Cloudomation resources.
  Ref: #2u55j9h
• Example web app based on Cloudomation
  Added an example to the documentation on how to create a small web application using Cloudomation as a backend.
  Ref: #26pxunv
• Implement method for webhook executions to return binary data
  Cloudomation webhooks can now return binary responses by using `webhook_bytes_response` or `webhook_base64_response`
  Ref: #861m9581g
• Notify about problems when an invalid value is entered in a YAML field
  When a YAML field contains a value which is not valid YAML, a warning and an error description is shown.
  Ref: #32qwjk7
• Workspace Configuration in the Workspace
  There’s now a UI screen for editing workspace settings easily.
  Ref: #28z2qbc

Bug Fixes

• 2FA configuration uses the same “subject” when using the same email address in multiple Cloudomation workspaces.
  In order to avoid 2FA authenticator applications overwriting existing entries, the 2FA subject will be appended with an unique ID.
  Ref: #29wjfbw
• Deleted resources are shown in the quick access menu
  Resources in the trash will now be shown only in the “Deleted” section of the quick access menu.
  Ref: #2vrm9q7
• Error when using the term “execution” or “message” in the quick search
  It was impossible to use only the terms “execution” or “message” in the quick search.
  Ref: #2ngdx10
• Resources of project were not deleted when project was deleted
  Only the first 1000 resources of a project were deleted when the project was deleted.
  Ref: #2tzjb2n
• Using an underscore symbol in the advanced search mangles the search term
  When using the underscore symbol in the advanced search term the first letter of the search term was cut off.
  Ref: #2vk0g68
• Using space in advanced search shown as percent symbol
  When using a space in the advanced search the search term was changed and spaces were shown as percent symbols.
  Ref: #867728mcy
• Flow-script visualisation failed to load when using a bare-except in the script
  The parsing of the script did not properly handle bare-except statements.
  Ref: #2vk0g68
• Cannot run flow with an incomplete static wrapper configuration attached
  It was not possible to run a flow which has an incomplete wrapper configuration attached. Now incomplete wrapper configurations are ignored.
  Ref: #861m964uf
• Misconfigured schedules might prevent workspace from starting
  Certain misconfigurations of schedules might cause a workspace unable to start. Processing of schedules is now deferred to a background task and log any misconfigurations.
  Ref: #2zb86z6
• Improper handling of multiple vault secrets in the same line
  Using more than one vault secret in the same line causes the first secret value to be used for all subsequent secrets too.
  Ref: #32j4jxp
• Unable to disable the use of TLS for the SMTP connection of the workspace
  Setting `SMTP_USE_STARTTLS` to `false` resulted in the default value of the library to be used: using TLS
  Ref: #32j46rc
• Failed to access vault secret which contains a dot symbol in the path
  The parsing of the secret path incorrectly handled dots.
  Ref: #32qumj0
• Interactive wrapper aborts if email cannot be sent
  If any email cannot be sent due to an error response from the SMTP server, the interactive wrapper used to abort. Now it will log the failing attempt and try to continue sending email to other recipients.
  Ref: #3338em5
• Racing condition in frontend when trying to save a message form
  Occasionally it was impossible to save a message form.
  Ref: #85zrgb6t0
• Cleanup of deleted executions uses the wrong configuration value
  Cleanup of deleted executions used the retention time configuration of deleted resources.
  Ref: #861m4kkje
• Cannot send email with non us-ascii characters in message body
  The workspace email integration expected only us-ascii encoded messages. A new configuration parameter `SMTP_CHARSET` was added to specify any character encoding for the message body.
  Ref: #861m9jg51
• Webhook cannot start execution if associated flow uses a static wrapper
  The handling of static wrappers prohibited the creation of executions for webhooks.
  Ref: #863fxnd0a
• Flow-API methods to maintain wrappers were missing
  It was not possible to create/update/delete wrappers using the Flow-API.
  Ref: #861menjgy