-
Spike
-
Resolution: Done
-
Normal
-
None
-
None
-
Future Sustainability
-
5
-
False
-
-
False
-
-
-
-
Installer Sprint 2025-67
-
None
Value Statement
When developing changes to an upgrade path in ACM, it is incredibly difficult to smoketest before a downstream build is created. If we can discover how to create a custom catalog source and custom ACM bundle image, then we can have two channels with which to actually perform a real upgrade scenario during smoketest.
Definition of Done for Engineering Story Owner (Checklist)
- [x] A bundle PoC has been created
Status
- I have used CLAUDE AI to successfully generate an ACM bundle image and a custom Catalog Source image in order to trigger a true upgrade scenario.
- I documented the whole process here https://docs.google.com/document/d/18kvMlyNLmEAmL8ciQSMonXtI7aF9ixb2Qs_cTa_toO4/edit?tab=t.0#heading=h.pets10nvz448
These two images depict an upgrade scenario change occurring: MCE has not been upgraded yet in the first image, and it has in the second image. This status block is new to the code I was testing at the time