What is new

The following new features are available in the Cloud Automation Manager 4.1.0.0 release on IBM Multicloud Manager 3.2.1 or 3.2.0:

What is new in Cloud Automation Manager 4.1.0.1

• Enhancements to service composer:

  • Supports upgrade or downgrade of a active service instance, see Upgrading or downgrading a service instance.

  • Supports specifying if the value of input parameter can be modified while editing a service instance, see Creating new input and output parameters.

  • Activity attribute in the service composition tab has changed from Immutable to Editable.

  • Unretire a service, see Unretiring a service version.

• Enhancements to Template Designer:

  • Support for modules from an unprotected URL.

  • Support for selection of data objects during provisioning.

  • Enable drag and drop of resources from the palette in the template source view.

What is new in Cloud Automation Manager 4.1.0.0

• Integrates Cloud Automation Manager and Ansible Tower allowing user to use the Ansible job templates in composing a service. For more information, see Ansible Tower Integration.

• CAM CLI Install tool (Technical Preview) allows the users to manage Cloud Automation Manager functionality using the terminal. For more information. see Installing CLI tool.

• Supports multiple Terraform versions that are offered when deploying the templates. This Cloud Automation Manager version ships Terraform 0.11 and 0.12 versions. For more information, see Managing Terraform Version.

• Supports Cloud Automation Manager Online Installation using IBM entitled Registry.

• Enhancements to Template Designer:

  • Supports deploying a Terraform template from the Template Designer included in the Cloud Automation Manager.

• Enhancements to Cloud automation content:

  • Supports OpenShift 4.2 for AWS and VMWare.
  • Supports new versions for all other templates and services to support IBM Cloud Pak for Multicloud Management 3.2.1.

• Enhancements to service composer:

  • Supports multiple versions for a service, providing flexibility when managing a service and the supporting end user needs. For more information, see Adding a service version.
  • Supports editing a deployed service instance, For more information, see Editing Service Instance.
  • Supports creation and execution of custom actions using the service composer composition tab.
  • Supports dynamic parameters which can be fetched dynamically in real time.
  • Supports creation and execution of custom actions against deployed service instance.
  • Improved view only experience for published services.

• Advanced Content Runtime changes in template version 2.6

  The newer versions of Chef require the user to get into an agreement with Chef if it is used for commercial purpose. When you deploy a new Advanced Content Runtime version 2.6 or higher or modify your existing deployment to use version 2.6 or higher, you would have to agree that you are either using older version of Chef or you have an agreement with Chef to use Chef for commercial purpose.