Release Versions

VMware Aria Automation| May 2024

VMware Aria Automation 8.17| May 14 2024

  • VMware Aria Automation build 23831516

  • VMware Aria Automation Easy Installer build 23838682

  • VMware Aria Automation Cloud Extensibility Proxy build 23787549

  • VMware Aria Automation Orchestrator build 23787547

Updates made to this document

Date

Description of update

Type

May 14th 2024

Initial publishing for VMware Aria Automation 8.17

For more information, see our blogs about the VMware Aria Automation releases.

Note: VMware has announced the End of Availability (EoA) of the VMware Aria SaaS services including VMware Aria Automation SaaS, as of February 2024. VMware will continue to support customers currently using VMware Aria SaaS services until the end of their subscription term. See VMware End Of Availability of Perpetual Licensing and SaaS Services.

Note: The VMware Aria Automation Cloud Extensibility Proxy build specified above is only applicable for on-prem VMware Aria Automation deployments. The last applicable cloud extensibility proxy build for VMware Aria Automation SaaS is 23103969.

About VMware Aria Automation

You can find information about these new features and more at VMware Aria Automation and in the signpost and tooltip help in the user interface. Even more information is available when you open the in-product support panel where you can read and search for related topics, and view community posts and KBs, that appear for the active user interface page.

Notice: Release Notes for previous releases are archived yearly:

Before you begin

Familiarize yourself with the supporting documents.

VMware Aria Automation

VMware Aria Automation 8.17

After setting up your users, you can use the Getting Started and Using and Managing guides for each of the included services. The Getting Started guides include an end-to-end proof of concept. The Using and Managing guides provide more in-depth information that supports your exploration of the available features. Additional information is also available in VMware Aria Automation product documentation.

After installing vRealize Automation and setting up your users, you can use the Getting Started and Using and Managing guides for each of the included services. The Getting Started guides include an end-to-end proof of concept. The Using and Managing guides provide more in-depth information that supports your exploration of the available features. Additional information is also available in VMware Aria Automation product documentation.

Automation Orchestrator 8.17

VMware Aria Automation 8.17 What's New

  • New VMware Aria Automation home page

    A new user dashboard is now part of the VMware Aria Automation home page to help users navigate through complex architectures as part of Automation Assembler for administrators. Whether a user is new to VMware Aria products, or they are a seasoned VMware Aria Automation user, they can find the dashboard useful for the following scenarios:

    • Provide an overview for cloud environments by segment and VM status.

    • Visualize an inventory summary broken down by cloud zone and projects.

    • Visualize a deployment summary with upcoming lease policy changes and recently expired policies.

    • Review recent in-product notifications and respond to requests directly.

    Note: The home page is the default landing page for Automation Assembler only if the administrator does not have a cloud account in the organization. Otherwise, the default landing page is the Resources page in Automation Assembler. For more information, go to How do I get started with Automation Assembler using the VMware Aria Automation Launchpad.

  • New Launchpad added to the VMware Aria Automation home page

    A new Launchpad is now available for users who are getting started with VMware Aria Automation or want shortcut access to commonly used actions. You can perform easy-to-learn use cases using the two guided workflows. The Launchpad covers the following use cases:

    • Add a cloud account: use your credentials to validate and link cloud accounts.

    • Apply lease expiration: create a lease policy to enforce resource expiration.

    For more information, go to How do I get started with Automation Assembler using the VMware Aria Automation Launchpad.

  • Cloud Consumption Interface (CCI) Supervisor namespace, TKG, and other resource support in the Automation Assember design canvas

    CCI on-prem was released in VMware Aria Automation 8.16.1. The current release introduces support for defining multi-tier applications in Automation Assembler templates by leveraging Supervisor namespaces, TKG clusters, and any other CCI resources. You can now run a catalog item containing CCI resources that was prepared by an administrator. This capability brings together CCI and the rest of VMware Aria Automation capabilities around Infrastructure as Code (IaC) and governance with policies. For more information, go to Automating Kubernetes-based workloads in Automation Assembler.

  • Integrating a single VMware Aria Operations on-prem instance with multiple VMware Aria Automation on-prem tenants

    A single VMware Aria Operations instance can now integrate with multiple VMware Aria Automation tenants running on the same on-premises appliance.

  • Day 2 action for unregistering a cluster of VMs

    Unregister day2 action is supported for cluster of VMs. Note that the action is unavailable on a single VM within a cluster that shares disk or disk cluster with other VMs.

  • Increased number of private cloud accounts in VMware Aria Automation

    With this release, we are increasing the number of supported private cloud accounts in VMware Aria Automation from 50 to 100. For more information, go to Scalability and Concurrency Maximums.

  • Content sharing policy now supports scope at the organization level and also enables role-based access control

    Starting this release, the content-sharing policy supports two enhancements:

    1. The ability to share content across the entire organization by setting the scope as Organization. The organization-scoped policies only affect shared VMware cloud templates (VCT).

    2. A Role-based access entitlement. This feature allows for content sharing between users based on their set roles.  The roles can be project administrators, project members, and named custom roles.

    These enhancements significantly streamline content sharing and access control within the organization. For more information, go to How do I configure Automation Service Broker content sharing policies.

  • New Active Directory (AD) error messages when changing projects

    When invoking the Change Project action on a deployment that is associated with an Active Directory integration, there are certain scenarios that will cause validation errors.

    When the source project is associated with an AD integration, but the target project is not associated with an AD integration. In such cases, you receive the following error message:

    "Target project is not associated with AD integration".

    To resolve this error, the target project must be associated with an AD integration that has the same organizational unit.

    Another possible scenario occurs when both the source project and the target project are associated with an AD integration, but the AD integration is not part of the same organizational unit. In such cases you receive the following error message:

    "The properties(OU, BaseDN) associated with the project did not match the project".

    To resolve this error, the organizational unit of the target project must be changed, or a new AD integration must be made to associate with the same organization unit.

  • Announcing intent to deprecate specific Kubernetes automation capabilities

    VMware by Broadcom is announcing the planned deprecation of Kubernetes integration capabilities, including the TKG integration and TMC integration documented under How do I work with Kubernetes in Automation Assembler. The actual deprecation and removal of these capabilities from the product will happen in a future release. Customers are encouraged to adopt the Cloud Consumption interface (CCI) and vSphere TKG IaaS service. For more information on CCI, go to Getting Started with the Cloud Consumption Interface in Automation Service Broker.

  • Announcing intent to remove deprecated automation capabilities

    VMware by Broadcom wants to remind customers that the following capabilities are deprecated and scheduled to be removed from VMware Aria Automation in a future release:

    • Support for NSX-V

    • Support for NSX-T Manager Mode

    • Support for NSX-V to NSX-T migration

    • Migration Assistant for vRealize Automation 7.6 to VMware Aria Automation 8.0 and later

    • Migration Assistant for NSX-V to NSX-T

    • Support for the VMware Aria Automation integration with vCloud Director

    Any customer currently leveraging these capabilities in VMware Aria Automation should make plans to stop using the relevant functionality.

  • Announcing intent to remove support of vCenter 6.x

    VMware by Broadcom wants to remind customers that the support for vCenter 6.x will be removed from VMware Aria Automation in a future release. Any customer currently using vCenter 6.x cloud accounts in VMware Aria Automation should make plans to upgrade to a supported version of vCenter.

Automation Orchestrator 8.17 What's New

  • License management is moved from the Control Center to the Automation Orchestrator Client

    License management for your external Automation Orchestrator deployment is now done from the Licensing page of the Automation Orchestrator Client. This page includes information about your currently applied license and the option to manually add a license. For more information, go to Automation Orchestrator feature enablement with licenses. As it is set to match the license in VMware Aria Automation, the Licensing page is unavailable in embedded Automation Orchestrator deployments.

  • The Command scripting object is removed

    The Command scripting object is removed and the 'execute' and 'executeAndLog' methods are deactivated. If these methods are invoked, they throw an exception. If your actions or workflows have scriptable task items that use this scripting object or methods, these scripts must be updated.

Resolved Issues

  • Unable to add a VMware Cloud Foundation (VCF) cloud account domain in VMware Aria Automation

    When attempting to add a VCF cloud account domain to VMware Aria Automation, you receive the following error message:

    "Something went wrong in a backend service."

    This error occurs when a user is adding a VCF cloud account domain in VMware Aria Automation while another domain creation is in progress in the SDDC Manager.

  • Rebuild fails with an error if the original VM image is no longer available

    Previously, a rebuild day 2 operation fails if the underlying image has been deleted at the endpoint. This is an issue for users who are unaware that the image is missing at the endpoint and the rebuild operation is blocked unless a new image reference is manually added from the back end for the machine.

    This issue is now resolved. When triggering the rebuild resource level day 2 action, if the image is missing, the user is prompted to select an image from the available list of image templates to rebuild the machine. 

    However, in case of the rebuild being performed at the deployment level, an available image must be manually patched on the machine properties and then the rebuild day 2 action can be attempted on the deployment. To do this, users must use the "__resolvedImageLink" and "_imageRef" input properties along with the relevant image value. Alternatively, users can trigger a resource level rebuild operation for that particular VM which will enable the user to select an image and rebuild the machine from the UI. 

  • Actions/{id}/bundle added to Swagger

    The actions/{id}/bundle REST API endpoint is added to the Automation Orchestrator Swagger documentation.

API Documentation and Versioning

Notice: Release Notes for previous releases are archived yearly:

API documentation is available with the product. To access all Swagger documents from a single landing page, go to:

  • https://<appliance.domain.com>/automation-ui/api-docs for vRealize Automation 8.x, where appliance.domain.com is your vRealize Automation appliance.

Before using the API, consider the latest API updates and changes for this release, and note any changes to the API services that you use. If you have not locked your API using the apiVersion variable before, you might encounter a change in an API response. Any API updates and changes are provided in the What's New section for each release.

For unlocked APIs, the default behavior varies depending upon the API.

  • For Cloud Assembly IaaS APIs, all requests which are executed without the apiVersion parameter will be redirected to the first version which is 2019-01-15. This redirect will allow every user who did not previously specify the apiVersion parameter to transition smoothly to the latest version without experiencing breaking changes.

    Note: For the Automation Assembly IaaS APIs, the latest version is apiVersion=2021-07-15. If left unlocked, IaaS API requests will be redirected to the first version which is 2019-01-15. The first version is deprecated and will be supported for 24 months. To ensure a smooth transition to the new version, lock your IaaS API requests with the apiVersion parameter assigned to 2021-07-15.

  • For other APIs, your API requests will default to the latest version. If you select one of the earlier version dates listed for the Swagger spec, the API behavior will reflect APIs that were in effect as of that date and any date until the next most recent version date. APIs are not versioned for every vRealize Automation release and not all APIs support the apiVersion parameter.

For more information about using the apiVersion parameter, see the Programming Guides listed in:

check-circle-line exclamation-circle-line close-line
Scroll to top icon