Release Notes for Cloud Manager in Adobe Experience Manager as a Cloud Service 2021.10.0 release-notes
This page outlines the Release Notes for Cloud Manager in Adobe Experience Manager (AEM) as a Cloud Service 2021.10.0.
Release date release-date
The Release date for Cloud Manager in AEM as a Cloud Service 2021.10.0 is October 14, 2021.
What’s new what-is-new
-
In preparation for some upcoming changes, existing deployment pipelines are now referenced and labeled in the user interface as Full Stack pipelines.
-
The pipeline card has been refreshed to display a single, integrated face that shows both production and non-production pipelines. Also, the user can select Run/Pause/Resume directly from the action menu associated with each pipeline.
-
A user in the Deployment Manager role can now delete the Production pipeline in a self-service manner by way of the UI.
-
Add and edit pipeline experiences have been refreshed to use familiar, modern modals.
-
Users of Cloud Manager can now submit feedback directly from the user interface by way of the Feedback button on top right of the landing page.
-
Yearly SLA Graphs can now be downloaded from the Cloud Manager’s user interface.
-
Code quality and non-production pipeline executions now use a more efficient shallow cloning process during the build step, leading to a faster build time for customers with especially large git repositories.
-
Add IP Allow List wizard now informs the user if the maximum allowed number of IP Allow Lists has been reached.
-
The Cloud Manager API documentation now includes an interactive playground that allows logged-in users to experiment with the API from their browser. See Cloud Manager API Playground for more details.
-
The tool tip on the Program card is more descriptive if a selection option under ‘Navigate To’ is disabled. It now displays “A production environment does not exist.”
Bug fixes bug-fixes
-
In rare situations, when an Adobe staff would restore a customer’s environment, the restoration was considered complete before the environment was fully operational.
-
Certain internal requests made during environment creation were not being retried.
-
If a deployment failed error occurs following domain name verification, the error message has been corrected to request the customer to contact their Adobe representative.