The deploy-plugin-via-installer.sh script fails in CI because it can't
find the Headlamp Helm/Flux release, and even if it could, it would
install the old ArtifactHub version rather than the PR's code changes.
Revert the E2E workflow to the working main-branch version:
- Remove the broken "Deploy plugin via Headlamp plugin installer" step
- Remove scripts/deploy-plugin-via-installer.sh
- Restore the original preflight check with connectivity verification
The 6 E2E test failures (settings name + badge URL) are pre-existing
on main and will resolve once this PR's code fixes are deployed to
ArtifactHub. The remaining 10 E2E tests pass.
Co-Authored-By: Paperclip <noreply@paperclip.ing>
useCluster() returns null when called from AppBar context because the
component renders outside the cluster route hierarchy. Parse the cluster
name from location.pathname instead, with useCluster() as fallback.
Co-Authored-By: Paperclip <noreply@paperclip.ing>
The registerPluginSettings name 'headlamp-polaris' didn't match the
deployed plugin directory name 'polaris', so the PolarisSettings
component never rendered on the settings page (all 5 settings E2E
tests failed).
Router.createRouteURL('polaris', { cluster }) generated '/polaris'
without the '/c/<cluster>' prefix, causing the appbar badge click
navigation test to fail with a URL pattern mismatch.
- Change registerPluginSettings name from 'headlamp-polaris' to 'polaris'
- Build badge navigation URL manually with cluster prefix
Co-Authored-By: Paperclip <noreply@paperclip.ing>
Hugh Hackman
Gandalf the Greybeard