Alexandre Alves
Alexandre Alves
FYI @nwmac @gaktive @richard-cox we've marked this as `backend blocked` and reached out to the proper team proposing a solution, but which would entail a backend change
**clock extension test:** _installs a version not latest -> let's call it `V1`_ https://github.com/rancher/dashboard/blob/master/cypress/e2e/tests/pages/extensions/extensions.spec.ts#L221-L245 _upgrades to latest -> let's call it `V2`_ https://github.com/rancher/dashboard/blob/master/cypress/e2e/tests/pages/extensions/extensions.spec.ts#L261-L280 _rollback -> going back to`V1`_ https://github.com/rancher/dashboard/blob/master/cypress/e2e/tests/pages/extensions/extensions.spec.ts#L282-L301 TODO...
Just merged https://github.com/rancher/ui-plugin-examples/pull/55 which should be the only dependency needed to re-enable the e2e for extensions (extensions.spec)
Item still relevant and blocking UI team initiative https://github.com/rancher/dashboard/pull/9644
still relevant
> The functionality should already by covered by the `/version` endpoint. @aalves08 can you verify if this will solve this issue for you? That seems to do the trick with...
may be related with https://github.com/rancher/dashboard/pull/9745 ?
@rak-phillip add pr comments addressed. Ready for another go
> We found a [regression](https://github.com/rancher/dashboard/issues/14762) introduced by current PR, @aalves08 could you take a look ? On it @torchiaf 👍
My main concern here is the variables names that change and even some new variables that come in... I've locally built two versions of Kubewarden: - one with the current...