| 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): |
|
