Release Notes

Want to see it in action?

Book a Demo

Version 7 "Gugelhupf"

2023-03-30

The „Gugelhupf“ is a cake and is known and loved far beyond the borders of Austria. In the past, a Gugelhupf was served at major events.

We are a Viennese company and we like sweets – therefore we name our releases after Viennese sweets. The „Gugelhupf“ can be prepared with a wide variety of ingredients. Cloudomation Version 7 shows, manages and tracks your „software-ingredients“: with the new dependency visualisation, the bundle manager and a new logging feature. But that’s not all. Check out the release notes for more!

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

  • 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

Bug Fixes

Version 6 "Palatschinke"

2022-10-20

To the surprise of some non-Viennese, „Palatschinken“ are a warm sweet dish – completely unrelated to savory „Schinken“. Flat and prepared in a pan, Palatschinken can be enjoyed with jam, ice cream or chocolate.

We are a Viennese company and we like sweets – therefore we name our releases after Viennese sweets. „Palatschinken“ are a versatile dish that can be prepared in many variants. It is this scrumptious flexibility that Palaschinken and Cloudomation have in common: a delicious concept that can be adapted to your taste just as you like it.

Breaking Changes

  • Executions are automatically deleted after a fixed expiry time
    Per default, all executions will automatically be deleted (i.e. moved to the „deleted“ section) after two weeks. From the „deleted“ section, all records are automatically deleted permanently after another two weeks. These expiry times can be configured in the workspace settings. For cloud workspaces, this is currently only possible via the REST API. For self-managed on-premise workspaces, this is also possible via environment variables. Please reach out to support@cloudomation.com if you need help adjusting these settings.
    Ref: #2884nj3
  • Delete operation moves records to “deleted“
    Per default all delete operations will move the deleted record to a “deleted” section (equivalent to a trash bin). Deleted records are read-only. Deleted records can be restored or deleted permanently. Deleted records will automatically be deleted permanently after a defined time. The default expiry time for deleted records is 2 weeks. This can be changed in the workspace configuration. In addition, per default executions and messages will automatically be moved to the deleted section after 2 weeks. This can also be changed in the workspace configuration.
    Ref: #2884nj3
  • Resource names must be unique across all types
    Names of resources now have to be unique across all resource types. Any existing name duplication will have to be cleaned up manually before upgrading to this version or the upgrade will fail.
    Ref: #2h72zy6
    The following flow returns all duplicate resource names in your workspace. Please rename or remove any duplicates before upgrading:
import flow_api
 
def handler(system: flow_api.System, this: flow_api.Execution):
   counts = {}
   for resource in system.resources(include_archived=True):
       resource_name, resource_type = resource.get('name', 'resource_type')
       counts[resource_name] = counts.get(resource_name, 0) + 1
   counts = {
       k: v
       for k, v
       in counts.items()
       if v > 1
   }
   this.log(counts=counts)
   return this.success('all done')

New Features​

  • Deleted Records
    Per default all delete operations will move the deleted record to a “deleted” section (equivalent to a trash bin). Deleted records are read-only. Deleted records can be restored or deleted permanently. Deleted records will automatically be deleted permanently after a defined time. The default expiry time for deleted records is 2 weeks. This can be changed in the workspace configuration. In addition, per default executions and messages will automatically be moved to the deleted section after 2 weeks. This can also be changed in the workspace configuration.
    Ref: #26py7ce
  • Advanced search
    The advanced search screen provides a unified search view for resources, executions and messages with the possibility to filter the results.
    Ref: #25cphdy
  • Flow script visualization
    Cloudomation generates a visual representation of the control-flow implemented in your automation scripts.
    Ref: #2fe02kg
  • Setup and update script for on-premise workspaces
    On-premise workspace installations can quickly and easily be installed and updated using the Cloudomation installer.
    Ref: #1znfng5
  • Mock wrapper
    For testing it can be useful to simulate a third-party system. The mock wrapper will return a response without actually calling a third-party system.
    Ref: #26pxvg5
  • Cache wrapper
    The cache wrapper will return previously fetched responses from third-party systems for a defined amount of time. This can be used to increase performance of automation scripts and to reduce load on third-party systems.
    Ref: #2hcy8by
  • Timeout wrapper
    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
  • Bundles
    Cloudomation provides bundles of commonly used functionality.
    Ref: #2hcynfh
  • Unified info field for execution live monitor
    The „info“ column in the execution live monitor provides a rich set of relevant information combined in one view.
  • Improved tables
    Table views now support column selection and sorting.
    Ref: #2fkgjp3
  • Renamed „Try“ to „Run in dev mode“
    Better alignment of wording.
    Ref: #2hjhj2w
  • Live-updates of existing projects and messages
    The list of projects, opened records and messages is now pushed by the backend and will update live when there are changes.
    Ref: #26pxpkd
  • Improved documentation
    Migrated to a new documentation library.
    Ref: #26pxvax
  • Read-only resources and projects
    Individual resources as well as projects can be set to read-only. Read-only resources can be used, but not modified.
    Ref: #26py048
  • DependencyFailedError makes failed execution available in execution object
    A commonly used pattern is to query the outputs of a failed execution. The execution attribute of a DependencyFailedError provides a quick and intuitive way to access the execution which failed.
    Ref: #26pxtnn
  • ISO3166 country-codes library available in flow api
    Flows can use the library to generate country names from ISO abbreviations and the other way around.
    Ref: #29ah2yv
  • Powershell (WinRM) connector support for Kerberos
    Kerberos authentication can be used to authenticate to a WinRM service.
    Ref: #2ajh619
  • AWS connector can upload files
    Text files, binary files or base64 strings can be uploaded to AWS APIs.
    Ref: #28zuuq5

Bug Fixes

Version 5 "Topfengolatsche"

2022-03-17

Topfengolatschen are a typical Viennes pastry with a moist, sweet curd filling wrapped in fine and crunchy puff pastry. A staple of Viennes coffee houses as well as bakeries, it is one of Vienna’s most common pastries. 

We are a Viennese company and we like sweets – therefore we name our releases after Viennese sweets. Topfengolatschen get their special taste through the combination of moist filling constrasting with the crunchy exterior. The Cloudomation Version Topfengolatsche comes with the powerful new „wrapper“ feature, which allows you to do the same with your automations: add a layer of crunchy deliciousness to your tasty flow scripts by wrapping them in retry, notification, iteractive use or custom wrappers. 

Breaking Changes

New Features​

Execution Live Monitor with Quick Filter
Execution Record with Embedded Message Form

Bug Fixes

Version 4 "Punschkrapferl"

2021-08-12

Punschkrapfen or Punschkrapferl (punch cake) is a classic Austrian confection of pastry with a fine rum flavor. It is a cake filled with cake crumbs, nougat chocolate, apricot jam and then soaked with rum.

We are a Viennese company and we like sweets – therefore we name our releases after Viennese sweets. „Punchkrapferl“ with their pink, glossy glazing are exceptionally pretty – just like release 4.0, which comes with a shiny new user interface.

Breaking Changes

New Features​

  • New User Interface
    Clearer, cleaner, easier: the new user interface lets you focus on getting things done, instead of searching for buttons. 
    Ref: CLOUD-5841

Bug Fixes

Version 3

2021-01-20

Breaking Changes

  • New resource: webhook
    Webhooks are now configured using a dedicated „Webhook“ resource type. Webhooks which are currently configured in a Setting must be migrated manually.
    Ref: CLOUD-3366
  • New input schema for Google connector
    the project ID should now be specified in the „params“ input
    Ref: CLOUD-5292

New Features​

  • Visual representation of dependencies
    The dependencies between executions can be visually represented in the Cloudomation UI.
    Ref: CLOUD-3636
6 sync products relations view
  • Visual representation of flow logic
    The control-structure logic of a flow can be visually represented in the Cloudomation UI.
    Ref: CLOUD-3635
  • Cloudomation workspace linking
    It is now possible to link several active Cloudomation workspaces and synchronize executions between them.
    Ref: CLOUD-3297
  • Execution savepoints & restore functionality
    Executions can revert to a previous state and continue running from there. This enables savepoints and restarts.
    Ref: CLOUD-22
  • Native git integration
    Git integration is now configured using a dedicated „Git config“ resource type. All Cloudomation resources can be synchronized from git.
    Ref: CLOUD-69
  • Native HashiCorp Vault integration
    Vault integration is now configured using a dedicated „Vault config“ resource type. Connections and Executions can refer to a secret path in a Vault installation. The secret is fetched at runtime and not stored in Cloudomation.
    Ref: CLOUD-827
  • New resource type: connection
    It is possible to preconfigure connections to third-party systems and re-use them in flows.
    Ref: CLOUD-2465
  • New connector: MSSQL
    It is now possible to connect to MSSQL databases.
    Ref: CLOUD-3205
  • On-premise support
    Cloudomation can be deployed on-premise with or without Kubernetes.
    Ref: CLOUD-105
  • REST connector can auto-retry on certain HTTP codes
    The REST connector will retry on HTTP 502, 503 and 504 per default. Custom codes and retry backoff and timeouts can be specified.
    Ref: CLOUD-3430 
  • New connector: VAULT
    It is now possible to connect to a HashiCorp Vault using the VAULT connector.
    Ref: CLOUD-3964
  • New connector: XMLRPC
    It is now possible to connect to any XML-RPC service.
    Ref: CLOUD-4498
  • Support for running Cloudomation on Windows
    Cloudomation can be deployed on Windows.
    Ref: CLOUD-4530
  • New connector: IMAP
    It is now possible to connect to IMAP servers to search and fetch emails.
    Ref: CLOUD-4581
  • New connector: LDAP
    It is now possible to connect to LDAP servers for authentication and to query data about a domain.
    Ref: CLOUD-4586
  • Support OAuth2 for bullhorn
    The Oauth resource now supports authenticating against a Bullhorn installation.
    Ref: CLOUD-4677

Bug Fixes

  • Code in finally block of flow is not executed when using `this.end()` in the try block
    The python try…catch…finally control structure can now be used by flows to run logic after an error occurs, when the flow aborts, is cancelled, or when the flow ends normally. This can be used to ensure the cleanup of dynamically created resources.
    Ref: CLOUD-1956

Version 2

2020-03-26

Breaking Changes

  • Changes in pricing
    Pricing based on productive executions of tasks replaced the token-based pricing model. Productive task executions are called “connections”.  The „Token Report“ section was removed from the UI.
    Ref: CLOUD-2145
  • Removed “inputs” resource
    The „messages“ and „inputs“ resources were merged into a combined resource called „messages“. The new messages resource provides additional functionality to design message forms to request a response from Cloudomation users.
    Ref: CLOUD-1622
Consolidated messages resource

New Features

  • Development mode
    Tasks can be executed in development and productive mode. Task executions (connections) in development mode are free of charge.
    Ref: CLOUD-2059
  • User Interface redesign
    The user interface was overhauled with a new color scheme and a cleaner design.
    Ref: CLOUD-2991
Cloudomation V2 design
  • Editable files
    Text files in the „files“ resource can now be edited in the Cloudomation UI.
    Ref: CLOUD-1480
  • Extended upload and download functionality
    Users can now upload and download flow scripts, settings, and files through the UI directly in the respective views.
    Ref: CLOUD-1306, CLOUD-2330
Writing file content in the user interface
  • Standard API documentation
    Cloudomation API now provides OpenAPI schema and SwaggerUI.
    Ref: CLOUD-2027
  • Advanced search in list views & REST API
    All list views in the UI and the Cloudomation REST API now support filter expressions.
    Ref: CLOUD-11
  • Filter expressions in flow API
    All flow-API list calls now support filter expressions.
    Ref: CLOUD-1646
  • Improved dependency overview
    Users can now see live which dependencies a flow script is currently waiting for, as well as which dependencies it waited for in the past.
    Ref: CLOUD-2044
  • Display of recent executions in flow record
    The flow record view now shows the last 3 executions of that flow.
    Ref: CLOUD-601
  • Two-factor authentication
    Users can now activate two-factor authentication for logging into Cloudomation.
    Ref: CLOUD-2558
  • Parse pdf in flow script
    Users can now parse the contents of pdf files directly in flow scripts.
    Ref: CLOUD-2525
  • REST multipart POST upload
    The REST task type now supports multipart post uploads.
    Ref: CLOUD-2524
  • Powershell task type
    Users can now access Windows machines via Windows Remote Management and execute Powershell scripts.
    Ref: CLOUD-1851
  • Kubernetes task type
    Users can now manage Kubernetes directly in flow scripts.
  • PostgreSQL task type 
    Users can now access PostgreSQL databases directly from flow scripts.
    Ref: CLOUD-1620
  • Google API task type with Oauth2 
    Users can now use all Google APIs, and authenticate against Google APIs with oauth2. 
    Ref: CLOUD-392
  • Email attachments 
    Users can now send emails with attachments directly from flow scripts.  
    Ref: CLOUD-1082
  • Created/modified timestamps for all records
    All resources now provide created at/created by and modified at/modified by fields.
    Ref: CLOUD-815
  • Protect API against denial-of-service
    The load-balancer now enforces rate-limits.
    Ref: CLOUD-699
  • Improved pagination display for long lists
    The pagination control will skip pages when there are more than 9 pages. The pagination will always show buttons for the first two pages, last two pages, two before the current page, and two after the current page.
    Ref: CLOUD-733
  • Changed database backend
    Improved scalability by migrating to PostgreSQL as a database backend.
    Ref: CLOUD-2016

Bug Fixes

  • Files resource now refreshes when modified
    In contrast to all other resources, the files resource did not push updates to the UI. This is now fixed.
    Ref: CLOUD-1086 Files resource does not refresh when modified
  • Order of opened records fixed on page refresh
    Previously, page refreshes changed the order of opened records. Opened records now stay sorted when the page is refreshed.
    Ref: CLOUD-1085 page refresh reorders open flows
  • Files resource can now handle several executions requesting the same file
    Previously, only one execution could request a file at any one time. 
    Ref: CLOUD-2612 file_futures cannot handle two executions requesting the same file at the same time
  • Cancelling paused executions now cancels them immediately 
    Previously, paused executions could only be cancelled after resuming them. 
    Ref: CLOUD-1429 cancel paused execution is done only after execution „resume“
  • Fixed sorting of numerical columns
    Sorting of columns of various types was fixed (numbers, timestamp, duration, filesize).
    Ref: CLOUD-136 sort number column as number (not string)

Version 1

2019-03-01