I would like to see a the full uds-core suite run form the nightly uds core workflow rather than the k3d-core-slim-dev bundle. One of the advantages of this test from a Zarf / uds-cli maintainer perspective is that the large surface area of these charts covers many potential use cases of our upstream tools which we may not test for. The full uds-core suite has a much greater surface area still, and I believe would be appropriate for a nightly test.
A good example of where this came into play was with the upgrade to Helm 4 in Zarf (zarf-dev/zarf#4350). By manually running the full suite with a build of uds-cli from my Zarf branch, I discovered a problem with Helm hooks due to an upstream change. There were no Zarf tests for Helm hooks previously. I've since added an e2e test in Zarf, but I would not have known to do so, without running the full uds-core suite.
I would like to see a the full uds-core suite run form the nightly uds core workflow rather than the k3d-core-slim-dev bundle. One of the advantages of this test from a Zarf / uds-cli maintainer perspective is that the large surface area of these charts covers many potential use cases of our upstream tools which we may not test for. The full uds-core suite has a much greater surface area still, and I believe would be appropriate for a nightly test.
A good example of where this came into play was with the upgrade to Helm 4 in Zarf (zarf-dev/zarf#4350). By manually running the full suite with a build of uds-cli from my Zarf branch, I discovered a problem with Helm hooks due to an upstream change. There were no Zarf tests for Helm hooks previously. I've since added an e2e test in Zarf, but I would not have known to do so, without running the full uds-core suite.