Tags: MA9521/dashboard
Tags
Fix for SideNav not collapsing when toggling the menu button The `expanded` prop of the `SideNav` component was incorrectly set as an object instead of a boolean, preventing the nav from being collapsed. Fix the state update so it's providing a boolean as expected.
Support specifying git revision on import resources Add an optional input for git revision on the import resources page. If blank the PipelineResource will automatically detect the default branch. Remove helper text below inputs and move content to TooltipIcon on the label instead for a cleaner UI.
Remove Secrets and ServiceAccounts pages Remove the Secrets and ServiceAccounts pages from the Dashboard UI, along with the associated Create Secret / Patch ServiceAccount functionality. These pages provide incomplete functionality, have little to no benefit versus using `kubectl` or other tools to manage `Secrets`, and incur a significant overhead in terms of code maintenance since they have to be handled differently (e.g. sanitisation of secrets in backend). Also remove the RBAC rules giving the Dashboard access to get/list/... Secrets in all namespaces. This should make the Dashboard's default permissions a lot more palatable for many users who were reluctant to give it access to this sensitive information.
Update empty state strings for consistency and accuracy Update the strings displayed on empty tables to be more consistent across resource types and also to be more accurate. Since we've added label filtering support the 'no resources found' message has been a bit misleading, it should really be 'no matching resources found'. This is even more obvious with the recent addition of status filtering on the TaskRuns and PipelineRuns lists. Update the strings used for all namespaces, cluster resources, and selected namespace empty states.
Suppress fetch-mock warning on fallback By default, `fetch-mock` will output a warning when a request is handled by one of its fallback mechanisms, e.g. `.catch()` In our use this provides very little benefit and adds a lot of noise to the unit test logs. Disable the warning in the test setup.
PreviousNext