Ya Dan Pei
Ya Dan Pei
/label cherry-pick-approved
it looks like all fields are marked as required (*) ,however user still can click`Save configuration` and resources got updated when any field is missing
QE run a regression testing of nav menus, no issues found - adding/removal of nav menus - pin/unpin of nav menus - nav menu highlights etc /label qe-approved
with `console.tab` extension and all required property defined, user can add tab to any specific page matching with `contextId`  /label qe-approved
/label cherry-pick-approved
@TheRealJon wheh navigating through manged cluster pages, it seems managed cluster pages can not be loaded successfully and I can see some errors in console log ``` I0920 10:01:32.237240 1...
tested again today - Enable multi cluster on Hub cluster - Import one managed cluster with name 'test-cluster-one' - Visit 'test-cluster-one' from All Clusters dropdown, check console pod logs and...
QE has verified the functionality and no issues found(detailed can be found from test case in JIRA) /label qe-approved
QE tested the changes, confirmed that plugin metadata field`dependencies` is now optional(plugin still work without `dependencies`) and no regressions(existing plugins with `dependencies` still work) /label qe-approved
tested the PR and confirmed that the 'Sample Error Boundary Page' is working as expected /label qe-approved