* Server-side pagination for home page clusters list and side bar clusters
- Functional Changes
- SSP now works after vue3 bump
- Home Page Clusters list now uses server-side pagination
- Side Bar clusters list now uses server-side pagination
- Wire in now supported sorting / filtering by id and name used for table columns
- Allow pagination to be enabled given a specific context
- Call findPage without persisting to store
- New Pagination Tools
- PaginatedResourceTable - Convenience Component, wraps ResourceTable with pagination specific props
- PaginationWrapper - Convenience class to handle requests for resources and updates to them (avoiding store)
- Regressions
- Side Nav menu ready state was `mgmtCluster.isReady && !pCluster?.hasError`, now ???
* Iteration
Note - prov clusters is broken (only fetches local) due to blocking pr. breals
- notPinned list
* Fix dupe inStore
- remove from resource list, put in resource-fetch (used also by pag res table)
* Two fixes
- changes namespaces kicked of side nav cluster requests (thought pinnedIds changed)
- fix generic lists re-fetching given ns filter changes (they don't have namespaced arg)
* remove comment, backport fix
* test fixes
* E2E: Ensure we wait for cluster entries to exist before clicking on them
* backport fix for local/api filtering
* Remove debug code
* Changes after review
* e2e fixes / debugging
* More e2e fixes
* More e2e fixes
* More e2e fixes
* Fix generic pages that filter on pagination
* Attempt to fix flaky vai test
* Fix after merge from master
* Updates following new indexed files
* Fix lint and test
* Changes given real cluster tests
- general fixes
- correct issue were sorting prov clusters on mgmt cluster props (issue in master as well...)
- bit the bullet, we now don't fetch all mgmt clusters on dashboard visit.
- there could be knock on affects, but we'd need to remove it sometime in 2.11....
* Fix issues with diplaying rke1 data in home page
- includes https://github.com/rancher/dashboard/pull/12881
* Fix unit tests
* first iteration to improve extension point for tabs (missing default mode = VIEW)
* add default _DETAIL for the extension tabs extension point so that they are not added to EDIT views as well, unless specified otherwise
* revert harvester change
- Functional Changes
- SSP now works after vue3 bump
- Home Page Clusters list now uses server-side pagination
- Side Bar clusters list now uses server-side pagination
- Wire in now supported sorting / filtering by id and name used for table columns
- Allow pagination to be enabled given a specific context
- Call findPage without persisting to store
- New Pagination Tools
- PaginatedResourceTable - Convenience Component, wraps ResourceTable with pagination specific props
- PaginationWrapper - Convenience class to handle requests for resources and updates to them (avoiding store)
- Regressions
- Side Nav menu ready state was `mgmtCluster.isReady && !pCluster?.hasError`, now ???
- Functional Changes
- SSP now works after vue3 bump
- Home Page Clusters list now uses server-side pagination
- Side Bar clusters list now uses server-side pagination
- Wire in now supported sorting / filtering by id and name used for table columns
- Allow pagination to be enabled given a specific context
- Call findPage without persisting to store
- New Pagination Tools
- PaginatedResourceTable - Convenience Component, wraps ResourceTable with pagination specific props
- PaginationWrapper - Convenience class to handle requests for resources and updates to them (avoiding store)
- Regressions
- Side Nav menu ready state was `mgmtCluster.isReady && !pCluster?.hasError`, now ???
* update vsphere machine config to use new networks endpoint
* update vapp options to reference network name not moid
* vapp wip
* clear out vapp config when switching to custom
* fix issue with labeledSelect in mode multiple by allowing the binding of the attribute to the element v-select
* Add test for component to emit the correct value as array
---------
Co-authored-by: cnotv <giuseppe.leo@suse.com>
* Add container resource limit tests
Add real case scenario for unit input component
Add input test for container resource limit
Add base unit to unit input test
Add blur test for container resource limit and unit input
Extend input tests to all cases
Add test case with parent passing value and update on emission
Update tests
Update tests to match emitters
* Add emitters for unit input
* Accept ID pairing with data suggestion fix
Co-authored-by: Phillip Rak <rak.phillip@gmail.com>
* Enable tests after fix
---------
Co-authored-by: Phillip Rak <rak.phillip@gmail.com>
* remove $set from AKS validators
* fix cruGKE not rendering
* fix most aks unit tests
* fix crueks and eks config unit tests
* fix eks networking and nodegroup unit tests
* fix gke unit tests
* fix consumption gauge test
* fix namespacefilter tests
* fix command and taints unit tests
* fix questions unit tests
* fix hpa and service unit tests
* fix registryconfigs unit tests
* fix job unit tests
* fix longhorn unit tests
* fix addextensionsrepos unit tests
* fix rke2 basics unit tests
* fix container shell unit tests
* fix last aks pool test
* fix mount tests
* fix namespace and pv unit tests
* fix codemirror unit tests
* clean up aks, boolean, namespacefilter unit tests
* fix namespacefilter test
* remove redundant test case
- Remove custom code, use new generic code that follows 'compact' concept
- Apply to all four fields in row
- Also fix a bug where selected verbs such that another row is shown would grow height of other inputs
Fix height of Create Project Resource Quotes input fields
- Vue2
- Component would inherit attributes, such as class from owning element. For example classes applied to `<Select` would be applied to the first element within the Select component
- $attrs property does not contain some properties from the parent, such as class
- Vue3
- Component does not inherit attributes of owning element
- $attrs property contains all propertiesof parrent, including class
- Bug
- We fixed part one, but not part two
- in Select we were applying class twice, manually to parent and then automatically to v-select
- solution is to fix part two (chop out class)
Updates the slot syntax to be more consistent with `CruResource.vue`. This should help with accurately rendering slot content when we iterate over component slots.
Signed-off-by: Phillip Rak <rak.phillip@gmail.com>
This defines the `canPaginate()` computed prop so that it can be accessed in the `labeled-form-element` mixin.
Signed-off-by: Phillip Rak <rak.phillip@gmail.com>
Richard Cox