Skip to content

14 December 2020 Release Notes

Version 1.1.194

Feature Highlights

New Setting Attaches Metadata to Runtime Containers

This release introduces a setting in order schedules where users can define annotations for Kubernetes infrastructure objects.

Annotations are metadata in the form of key/value pairs that tools and libraries can retrieve at runtime. For example, the field could be used to attach AWS IAM role information so that the Automation platform can assume the role and access external resources.

Find the field in the Schedules tab on the Recipes or Variation pages, or add it manually to a recipe's variations.json file. See Configure Schedules for more information. [DEV-7447, DEV-7455]

()

New schedule setting adds annotations to runtime elements.

variations.json

{
  [File contents truncated for example]

  "mesos-setting-list": {
    "default": {
      "schedule": "now",
      "annotations": {
        "annotation1": "value1"
      }
    }
  }
}

The platform records an annotation entry in the recipe's variations.json file.

Other Fixes & Enhancements

Active Orders Promoted as "Stopped" from Deleted Kitchen: When a user deleted a kitchen and chose to promote order runs to the parent kitchen, the system transferred any orders that were scheduled for repeat order runs with a status of active in the parent. Those promoted orders were not, in fact, actively producing new order runs, and users would not necessarily want them to run in the parent kitchen anyway. This issue has been resolved, and scheduled orders now appear as stopped after promotion to a parent kitchen. [DEV-7248]

Optional Amazon Connection Property Added: Data sources and sinks that use the supported Amazon S3 and Amazon Redshift connectors can now accept an additional parameter that allows for assuming IAM (AWS Identity and Access Management) roles. The new aws-session-token property enables a workflow to perform actions across different AWS accounts, regions, and buckets. See the Amazon S3 or the Amazon Redshift/PostgreSQL connector topic for more information. [DEV-7154, DEV-7382]

Override Variables Handle Special Characters: Some syntaxes used with override variables were generating errors in the system. The presence of apostrophes and other special characters in override variables caused problems at order runtime and required users to recreate orders. This issue has been resolved with a change in how order processing initiates. [DEV-6230]

Container Events Display as Proper Logging Levels: The order run logs categorized warnings, errors, and other events returned from containers as entries at the INFO logging level. The actual event displayed properly within each entry, but users could not filter on those events. This issue has been resolved with an update to order run logging that translates container events to the proper levels. [DEV-6586]

  • Previous entry example:

INFO [Oct 19 09:48:38] AC: 2020-06-19 13:48:38,115 ERROR : Please add the following keys to azureblobConfig: {'connection_string'} - Post-fix entry:

ERROR [Oct 19 09:48:38] AC: 2020-06-19 13:48:38,115 ERROR : Please add the following keys to azureblobConfig: {'connection_string'}

List Variable Logging Skipped to Prevent Incomplete Logs: When a single order run log entry exceeds 1 KB, the log automatically truncates. The primary cause of any logs exceeding the limit is the output of the runtime variable, PreviousOrderRunIdList. The result of hitting this limit is that important troubleshooting information can become inaccessible to users. This issue has been resolved by no longer recording the list output of that variable. If needed, users can access this information with the Runtime Variables function in the Order Run Details page toolbar.  See Order Run Details for more information. [DEV-5653]

Jinja Load Functions Compile Correctly at Runtime: When implementing a Jinja load function in a variable defined in variables.json (shown in the example below), users found that file contents were not compiling at runtime. The variable would show file content with a manual compile in the File Editor, but the Runtime Variables dialog in the Order Run Details page displayed "None" for the variable value. The problem occurred with the load_text, load_json, and load_csv functions. This issue has been resolved so that Jinja load functions, used in variable or override declarations, compile correctly at runtime. [DEV-7241]

variables.json

{
    "variable-list": {
        "fileText": "{{load_text('some_file.txt')}}"
    }
}

Platform Accepts Warnings During File Decryption: An order run retrieving an encrypted file from an SFTP source was failing on a warning generated by GPG (GnuPrivacy Guard encryption standard) about an unsecured method. The platform was interpreting the warning as an error, causing the order run to stop. This issue was determined to present a low security risk and has been resolved with a code update to ignore warnings passed by GPG. [DEV-7440]

Warning

Customers Should Use the Latest Version of GPG: If using file encryption, ensure that your GPG encryption method is up to date and passes your vulnerability tests.