Product ideas | Community
Skip to main content

Filter by idea status

10000 Ideas

Provide a "upgrade.log" in cloudmanager with timestamp, version before and after the upgrade, identity triggering the upgrade, nlink to release notes, and notes (eg. ticket though which an upgrade was requested),New

Request for Feature Enhancement (RFE) Summary: In order to troubleshoot issues effectively each AEMaaCS should expose an upgrade log so development team can debug issues effectively (i.e. there was no feature deployment and something stopped working all of a sudden).   Information I'd like see inside:- timestamp- AEMaaCS version/release prior to and after the (up|down)grade - who (or what; mind that RO/RV is out there) scheduled/triggered a deployment- is given version already deployed or a deployment has to take place to enforce that- notes (i.e. if the upgrade was requested via support ticket then I'd love to see a reference to that)   Moreover it'd be great if such a log is available via Cloud Manager API (1 per environment). Use-case: Identifying if, why and though whom an upgrade was executed (also to analyze why some feature "suddenly fails") .If a feature fails to work through an upgrade - this is impossible to determine or debug. Current/Experienced Behavior: If a feature fails to work through an upgrade - this is impossible to determine or debug. There is no way to identify an environment has been upgraded, when , for what reason and by whom. Improved/Expected Behavior: Ability to review the upgrades, eg. through an "upgrade log" (available for download and "Tail"):* timestamp * version before  the upgrade * versions after the upgrade * identity/person/process triggering the upgrade * link to release notes * notes (eg. ticket though which an upgrade was requested), Environment Details (AEM version/service pack, any other specifics if applicable):   Customer-name/Organization name:   Screenshot (if applicable):   Code package (if applicable):  

AEMaaCS version information: being able to determine current version, latest version and being able to upgrade envrionments (dev) though CLINew

Request for Feature Enhancement (RFE) Summary: At the time of writing AEMaaCS environment API [1] does not allow me to: inspect which version of AEMaaCS given environment runs check if the version I have is the latest upgrade the environment programmatically. The only way to do it is via Cloud Manager Web UI (non PROD envs) or support ticket (STAGE/PROD). The latter may not be something Adobe considers doable (due to RO/RV), but we'd love to see such a feature for lower level environments. We has dozens of dev environments spread across multiple programs, so it is cumbersome to keep them in sync [1] https://developer.adobe.com/experience-cloud/cloud-manager/reference/api/#tag/Environments Use-case: enable to "automate upgrades" and across many  programs and environments (customers with up to 10 programs) - and to understand current and latest available verison. Current/Experienced Behavior: API and CLI do not provide information on * current AEM version of environment * latest available version provided for the environment * ability to execute upgrade though API/CLI Improved/Expected Behavior: API and CLI should offer the option to request * current AEM version of environment * latest available version provided for the environment *  execution of an upgrade (add upgrade flag and execute full-stack-pieline)  Environment Details (AEM version/service pack, any other specifics if applicable):   Customer-name/Organization name:   Screenshot (if applicable):   Code package (if applicable):