Version 11 "Zimtschnecke"

Breaking Changes

• The scheduling feature was simplified:
  • Configuring a schedule is now possible via a form.
    Ref: #86bzp0x9a

• • The schedule configuration was incorporated into the schedule record, removing the need for a separate schedule configuration setting. The default scheduler included in the scheduling bundle automatically migrates schedule configurations to the new schema.
    Ref: #86c0yv6kv
  • Schedules now show their next runs. The next runs are displayed on the schedule itself, as well as in list views that show schedules.
    Ref: #86c0yv6kv

• The MS Teams connector has been removed due to the functionality being retired by Microsoft. See their announcement: https://devblogs.microsoft.com/microsoft365dev/retirement-of-office-365-connectors-within-microsoft-teams/
  Ref: #86bzjt5km
• Removed text and html arguments from user.send_mail, they are insecure and html_template and html_data should be preferred. Added system.send_mail to send emails to multiple Cloudomation users.
  Ref: #86c0xa7yg
• Changed the format of configuration value LOGGING_CURRENT_LEVELS. The config value now accepts structured data instead of a string. Old values from release-10 will still work, but it won’t be possible to save config values in the old format.
  Ref: #86c0ar467
• Input arguments to wrappers were reduced. Previously, the workspace would apply default inputs to the original input argument set and pass that to the wrapper. Now, only the arguments received by the execution are passed on to the wrapper.
  Ref: #86c1qqjrw
• For connectors that can write files (imap, scp, ssh, ftp, sftp, scp, smb, rest), the way the file location is specified has been changed. File locations are now specified with a dictionary instead of a string. This allows specifying the exact location of the file.
  Ref: #86bya01ta
• Bundles can now contain executions.
  Ref: #86c10wnf8, #86c12ze7k

Deprecations

• The allow_empty and skip_empty flags controlling git commit behavior have been replaced by no_change_behavior. The old values are still accepted but scheduled for removal. The new argument accepts the following values: “Fail”, “CreateEmpty”, “Skip”
  Ref: #86c3pv0jy, #86c3a2x95

New Features

• The git integration has been improved significantly:
  • A “track_in_git” flag was introduced. Only records with the track_in_git flag set to true use the git integration. The flag can be edited in the details panel of every resource in a git-enabled project. This makes it possible to disable git tracking for records in git enabled locations.
    Ref: #86c1mhyma, #86c19cuwh, #86c1rr7zn, #86c1umbyq, #86c1rv2r4
  • The git icon on a git-enabled project, workspace or bundle screen now shows a count of records with uncommitted changes in that location.
    Ref: #86bzv11qw, #86c02tcye

• • When deleting a git-enabled project or bundle, a warning is now shown informing the user that this will also delete the git repository.
    Ref: #86c02vkyu
  • Commit messages are now sorted by their timestamp in the bulk commit dialogue.
    Ref: #86c04t4zn
  • It is now possible to reset records to their status in git. This can be done on individual records, and as a bulk action via the bulk commit dialogue.
    Ref: #86bzxnmg9, #86c1afu6k
  • Commits are now asynchronous.
    Ref: #86c116rv9
  • The git repository name can now be changed independently of the project/bundle name.
    Ref: #86c0g3wgw
  • Excessive consecutive changes to a resource will now track only the last git change instead of every edit. This eliminates duplicate entries in the autogenerated commit message and improves performance for commits significantly.
    Ref: #86c2evbr7, #86c23avh4
  • Git lock events are now displayed in the logs of affected records.
    Ref: #861mx97gt
  • Importing resources into git-enabled locations is now significantly faster.
    Ref: #86c31km2d
• All records can now have metadata attached to them. Metadata is displayed in the metadata tab and can be arbitrary data stored with any record.
  Ref: #30k4etf, #86c18uerc

• A new OVH connector has been added to create and manage cloud resources in OVH cloud.
  Ref: #86c4ttt4w
• The frontend now displays the current location of all resources as breadcrumbs in the UI.
  Ref: #275vpxk
• The Cloudomation Installer now includes functionality to optionally deploy a Hashicorp Vault. It also optionally creates a service that unseals the vault at startup.
  Ref: #2yu2fee, #86c2aneca
• The PS connector now handles cancellations, timeouts, and connection interruptions.
  Ref: #32qtn53
• Table views now remember selected columns, order, and page size in the browser.
  Ref: #867736rdp
• Locking and releasing a lock now creates log entries on executions and settings.
  Ref: #861mx97gt
• Restoring a record from trash will now also implicitly restore its container (project or bundle) if it was in the trash too.
  Ref: #861mxf48n
• It is now possible to change the read-only flag using a bulk action in list views.
  Ref: #86by29j3y
• Record descriptions can now be formatted with markdown.
  Ref: #86bzbr2hd
• The data field of log entries can now be searched in the workspace logs, in all log tabs and in the advanced search.
  Ref: #86bxqxrfc
• The display and UX of adding a wrapper to resources was improved. Wrappers are now shown in a tab and adding a wrapper is done via an “add wrapper” button.
  Ref: #86bxa4r82, #86bztza5y

• It is now possible to specify an input value in the “run with options” dialogue.
  Ref: #86bxktx23
• Passwords can now be multi-line, e.g. the password for an ssh key.
  Ref: #86bzgndw5
• Already installed bundles can now be re-installed, making it possible to reset them after local changes.
  Ref: #86c012te2
• Managing users and roles was made easier. It is now possible to add users to roles as well as roles to users.
  Ref: #86byxe3kp
• It is now possible to set the execution location for executions on a more granular basis.
  Ref: #86c082n9j, #86c082n2y, #86c14wnub
• The script tab of executions will now scroll to the line currently being executed while the execution is running.
  Ref: #86c0fd7xe
• The “latest executions” of connectors now have a “show all” button which allows to list all previous executions of that connector.
  Ref: #86c0h57g9
• A syntax error badge can now be displayed on all records which have scripts.
  Ref: #86c0fuu17
• Schedule, wrapper and flow executions now show the name and a link to the scheduler, wrapper or flow in the details panel.
  Ref: #86c0hx54m
• Custom objects can now have a before-create flow. This can be used to calculate default values.
  Ref: #86bzvtgk9, #86c0jy4b0
• It is now possible to restart executions without using savepoints. A “re-run executions” button is displayed on every execution that has ended.
  Ref: #86by9zp0y
• A “connection report” bundle was added. When installed and enabled, a “count connections” button is displayed on all executions that does an ad-hoc count of productive and dev-mode executions. In addition, a “count connections” wrapper allows continuous counting and tracking of executions for flows, connectors, wrappers and schedulers.

• Leading and trailing white spaces are now allowed in record names.
  Ref: #86c0pt3pq, #86c0pt59g
• Creating a new resource now opens a resource creation dialog, instead of creating the resource right away.
  Ref: #86bygh1c9
• Workspace settings are now configured with form fields (and not just plain text input fields).
  Ref: #862kpnxgq
• The currently opened resource is now always scrolled into view in the left-hand menu.
  Ref: #86c01p4mz, #86c0pft1j, #86c0pghyb
• The ssh connector now supports tunneling and port-forwarding.
  Ref: #861mzkb1d
• Schedulers, settings and custom objects now have a tab which lists other resources that use them:
  • Schedulers list schedules that reference this scheduler in a “used by” tab.
    Ref: #86c0jn353
  • Settings list executions that currently reference the setting as a lock. The tabs are called “holding the lock” and “waiting for lock”.
    Ref: #86c0jn5p9
  • Custom objects list other custom objects that reference them in a “used by” tab.
    Ref: #86c087j12

• Added dedicated datetime and time fields for various inputs
  Ref: #86c1q66bk, #86c1cu2d6, #86c1xfjfj
• All executions now have a maximum runtime after which they are cancelled. The default maximum runtime is configured in the workspace setting “DEFAULT_EXECUTION_MAX_RUNTIME_MINUTES”. In addition, a maximum runtime can be set individually in the details panel on every executable resource (flows, wrappers, schedulers, connectors), as well as on individual executions. If the execution runs longer than the maximum runtime, the execution is cancelled.
  Ref: #86c1uqzu0
• List views can now show more columns.
  Ref: #86c0q4bmc
• Bundle content is now marked explicitly with a “bundle content” badge. Content can be located in a bundle without being bundle content (e.g. executions). Only bundle content is affected by bundle operations such as updating or re-installing a bundle.
  Ref: #86c1y0n11

• Settings now have a logs tab.
  Ref: #861mx97n7
• The SFTP connector now supports list and delete.
  Ref: #86c10xdj5
• Cloudomation files are now stored in the filesystem on the Cloudomation host. This speeds up working with files and makes it possible to store and work with significantly larger files than before. Previously, files were stored as binary blobs in the database.
  Ref: #86c0jyn2w
• Recent executions are now prioritised.
  A new configuration setting “EXECUTION_RECENT_HOURS” controls which executions are considered “recent”.
  Ref: #86c4a2xcz
• A warning is displayed when many user interfaces are connected to the workspace simultaneously. This is to avoid a potential negative performance impact caused by many connected user interfaces.
  Ref: #86c46tp9c
• The default for ON_SAVE_MIGRATE_DEPRECATIONS_ENABLED has been changed to false.
  Ref: #86c29gund

Bug Fixes

• It was possible to modify an already ended execution.
  Ref: #2vycq3j
• Saving an object template no longer reloads the page twice.
  Ref: #86bz4x7yg
• The create menu only shows records a user has permission to create, instead of all record types.
  Ref: #86by8xnq9, #86bzeu7kt
• Copying the code of a log entry using the provided button would always copy the code of the last log entry.
  Ref: #86bzm0vaz
• It wasn’t possible to maximize and resize the code editor of read-only records.
  Ref: #86bzwgrfj
• Static wrapper schema forms didn’t enforce required fields.
  Ref: #862kjbmbq
• Prevent two imports of the same bundle running in parallel.
  Ref: #86bzzgav2
• The maximum character limit of 128 for record names was not enforced in the UI.
  Ref: #86bz4y9yv
• Switching a branch didn’t update the resource list of projects.
  Ref: #86c0fwy2m
• Disallow uninstalling bundles in the bundle manager if they are local (weren’t installed from a repository).
  Ref: #86c0p1nwe, #86c2eh150
• It was possible to modify breakpoints in read-only flows.
  Ref: #86c0q5cqy
• Changing a project icon marked all its resources as changed.
  Ref: #86c0pwcdp
• It was possible to remove the setting or the scheduler key from an enabled schedule. It is now impossible to edit an enabled schedule.
  Ref: #86by8v2za, #86c1b1mb7
• Large input/output values could crash the browser.
  Ref: #86c172u0j, #86c17zf5x
• It was impossible to cancel the powershell connector.
  Ref: #32qtn53
• The sort direction of modified_at in lists could not be changed.
  Ref: #86c1x9p4w
• Input and output values of executions weren’t shown for executions in the trash.
  Ref: #86c25e7zb
• Duplicating a flow didn’t duplicate subrecords (like the new metadata field).
  Ref: #86c209hfq, #86c2arm9r
• Specifying the vault_url for a vault config with a trailing slash crashed the integration.
  Ref: #86c2a595z
• Long-running git commits could time-out on the browser side and cancel the running commit in the backend. Changed to asynchronous commits.
  Ref: #86c2an5zd, #86c2evbr7
• Fixed various git related racing conditions which led to confusion. The underlying issue was a consistency safety check to avoid data loss. If a user performed to manny actions in quick succession, that safety check would fail and generate cryptic – non-obvious error messages. This safety check has been removed.
  Ref: #86c2xw6g3
• Allow import of fields “bundle_name”, “project_name” and “workspace_name” in addition to the respective *_id fields.
  Ref: #86c2ym3zq
• It was possible to “duplicate” a user via the flow_api.
  Ref: #86c3q6yne
• The flow_api “wait” parameter accepted strings and failed silently.
  Ref: #86c416mx7
• The return_when parameter returned an internal error when providing a bad argument.
  Ref: #86c22efpt, #86c49m2mp
• Setting the output of an execution to a non-json serializable data structure failed silently.
  Ref: #86c3zu2u8
• The provisioning status of a custom object created via a flow script wasn’t shown in the UI.
  Ref: #86c472zmf
• The list of custom objects on the corresponding object template page showed only the first 10 objects and displayed the total count of objects displayed, not the total of all items.
  Ref: #86c4nm9ww
• The “Reset to default” button on input value forms sometimes was incorrectly disabled.
  Ref: #86c0tbg2u
• Saving some wrappers would scroll the view to the bottom of the page.
  Ref: #86c0pyq68
• Scrolling over a page sometimes stuttered.
  Ref: #86c0pgqnp
• Secrets would remain shown on read-only forms when unfocusing the secret element.
  Ref: #86c107e9r
• Migrating connectors in flow scripts didn’t work if the connector_name was specified as a keyword argument instead of a positional argument.
  Ref: #86c114kc0
• The migration to the new input format for the SMTP connector did not correctly migrate attachments.
  Ref: #86c1uc3fy
• Lost executions would not be resumed if they were waiting for a dependency.
  Ref: #86c1um11g, #86c23duay
• Wrappers were not used if specified via the run with options dialog.
  Ref: #86c22nckr
• Excessively long git commit messages could cause the commit to fail. They are now truncated.
  Ref: #86c237gun
• Authentication would succeed if an OTP code was given but not required.
  Ref: #86c214xvh
• Fixed the migration for the SMB connector. It produced a port as a string instead of an integer.
  Ref: #86c241478
• Executions would get stuck if they received a datetime.date object in their inputs.
  Ref: #86c262mz3
• The MSSQL connector would crash if it expected a result, but found none, returning an internal error.
  Ref: #86c24tryj
• The PS connector accepted a missing host and would crash subsequently.
  Ref: #86c22ghh3
• The rest connector would write the server response to the specified cloudomation file, even if the request failed (Bad Gateway, for example).
  Ref: #86c235xj9
• Catch various SMTP connector errors which would be reported as internal errors, but are configuration or (SMTP) server errors. They are now reported correctly.
  Ref: #86c2631rf
• Fixed a racing condition for git commits. If two commits would run simultaneously one of them sometimes failed due to missing changes.
  Ref: #86c24thxt
• Fixed the schema migration for the SMTP connector.
  Ref: #86c29hbek, #86c29n1b2
• Long-running executions would restart from the beginning in certain situations, specifically if they ran for longer than SAVEPOINT_RETENTION_TIME_MINUTES.
  Ref: #86c2vz5my
• Making a record read-only and changing it back to writable discarded all unsaved data in the form.
  Ref: #86c0pwhfz, #86c0pwhza
• Specifying a branch name not conformant to git-check-ref-format returned a cryptic git error.
  Ref: #86c0pz10k
• Improved the delete and import logic for projects and bundles. They were frequently unable to delete projects and bundles which had references to other records, or contained records with referred to others.
  Ref: #86c0uma13, #86c0um16v, #86c0t5cph
• It was impossible to import read-only records.
  Ref: #86c0ukzfb
• Resetting a project to the status in git and thus causing the a renamed resource to be named back to its original name would change the internal id of that resource, causing other issues. The id is now kept consistent.
  Ref: #86c0pz469
• The LDAP client_key was exposed via exports and git. It’s a secret and no longer exposed.
  Ref: #86c0w0yb7
• The SSH and SCP connectors did not accept hostkeys without the hostname prepended.
  Ref: #86c0xqmz3
• The commit and bulk commit buttons were always disabled on the workspace.
  Ref: #86c0vwj2v
• The advanced search would not list records in the trash.
  Ref: #86c0t5hua
• Read-only settings could not be locked and the corresponding executions would wait forever. These settings can now also be locked.
  Ref: #86c10xdj5
• Saving an invalid public ssh key would result in an error but still save it.
  Ref: #86c0vwe74
• The speed of loading the dependency visualization has been improved significantly.
  Ref: #86c41px9a