Knowledge Base  /  Release Notes  /  2020
Knowledge Base  /  Release Notes  /  2020

Cloud Platform - Release Notes: March 3, 2020

Updated by Craig Wedbush on Mar 03, 2020
Article Code: kb/1285

Announcements (3)

Application Lifecycle Management

Support for running ALM agent as a non-root account

Application Lifecycle Management has added support for running the ALM agent as a non-root account in Linux-based VM instances. Users can find the configuration under the configuration tab of the provider details page. Users can also specify the mode in which the agent will execute any event. There are three modes that the user can configure this option:

  1. Run as Admin
  2. Run as a specified user (If the user does not exist, user will be created during the bootstrapping of the agent for a new instance)
  3. Automatic (Agent will try to execute as root if it has permissions to do so, otherwise, as the current user)

These settings are applied to all instances deployed into the provider and can be overridden at instance level once it has deployed. Every time there is a new event to execute, the agent will use the previously chosen user and mode to perform the event.

Support for the GCP US west (Salt Lake City, Utah, USA) region

Application Lifecycle Management now supports another Google Cloud Platform (GCP) region: US west (Salt Lake City, Utah, USA) and its corresponding availability zones, with the API name of us-west3. Once you synchronize your Google Cloud provider in Cloud Application Manager, you will be able to select any of the three availability zones of the new region in your Deployment Policy boxes. This applies to the current GCP bring your own cloud support.

New CloudFormation types supported

Application Lifecycle Management now supports additional CloudFormation types to be used in CloudFormation template boxes.

These additional types are:

  • "AWS::Config::ConformancePack"
  • "AWS::Config::OrganizationConformancePack"
  • "AWS::EC2::LocalGatewayRoute"
  • "AWS::EC2::LocalGatewayRouteTableVPCAssociation"
  • "AWS::FMS::NotificationChannel"
  • "AWS::FMS::Policy"

Users can now use these new resource types in the template definition of any CloudFormation template box or update any existing template instance to use it.