Knowledge Base  /  Release Notes  /  2018
Knowledge Base  /  Release Notes  /  2018

Cloud Platform - Release Notes: December 11, 2018

Updated by David Gardner on Dec 11, 2018
Article Code: kb/1175

Enhancements (7)

Cloud Application Manager

Application Lifecycle Management

Support for Google Compute Deployment Manager

Application Lifecycle Management now supports a new type of template box based on Google Deployment Manager Templates. Now you can create this new type of template box and add multiple Google Deployment templates files in YAML format to it to compose your box. Similar to the current support for AWS Cloud Formation, Azure ARM and Terraform templates, you can also define variables through Cloud Application Manager user interface, and then reference them from any Google Deployment Manager template file in the instance, with the usual Jinja format. For more information, please refer to https://www.ctl.io/knowledge-base/cloud-application-manager/automating-deployments/google-deployment-manager.md

Instances page now displays Azure native services

Application Lifecycle Management Instances page will now list Azure native services instances, classified by Compute, Storage, Network, Database and Other types. These instances will display basic information for each type, such as subtype, region, status, name and description. A great advantage for users is that they will see at a glance all Azure instances in Cloud Application Manager user interface.

Search by hostname in instances list

Application Lifecycle Management now supports searching by hostname in instances list, in addition to the already existing searchable fields: name, instance-id, service-id, public or private IP address, support_id or hostname fields_, or also by the owner or last user who acted on the instance.

Improve new instance detection procedures

Application Lifecycle Management has improved its new instance detection procedure, to avoid automatic registration of cloned machines under the former existing instance. The auto-detection and registering will still work as usual for auto-scaling out events, but will prevent any other unwanted use case to be self-registered.

New system variable service.provider_type

Application Lifecycle Management now supports a new Jinja System Variable to allow access the provider type where the instance has been deployed to. You can refer to this new variable through the usual Jinja syntax by referencing: {{ service.provider_type \}}. The returned value will be the corresponding descriptive name of the provider type, for example: "Amazon Web Services".

New Cloud Formation types supported

Application Lifecycle Management now supports additional Cloud Formation types to be used in Cloud Formation template boxes. These additional types are:

'AWS::ServiceDiscovery::HttpNamespace', 'AWS::Lambda::LayerVersion', 'AWS::Lambda::LayerVersionPermission'

The user can now use these new resource types in the template definition of any Cloud Formation template box, or update the template file of any existing template instance and reconfigure it to use the new resource types.