* rename variables
* change button names + fix import
* apply pagination to secrets
* Major Changes
- secrets and project scoped secrets are now two pages
- this fixes the issue where resource-fetch and associated mixins just fail with two of the same type on page
- incremental loading would have been broken for both
- project scoped secrets
- now correct lists upstream secrets that a project scoped based and on the target cluster
- lots of work to get CRUD for management secrets in explore/cluster world
- also includes a specific page to override the store for create/edit/view
- these are now correctly grouped by project
- updated to work with SSP enabled
- secrets list
- shows if the secrets comes from a project
- shows if the secret is a project scoped secret (only used on upstream cluster)
- updated to work with SSP enabled
- disabled update/delete of secrets created from project scoped (these just reset when sync runs again)
- disabled new detail view
- this is broken, it ignores both storeOverride and currentStore, always going to `cluster` store
TODO:
- mostly testing
- blocked on some BE issues (bugs, additional indexed field)
* ... progress. will update commit message
* Revert "Merge pull request #14748 from richard-cox/revert-project-secrets"
This reverts commit be3962261d, reversing
changes made to 62d80084d9.
* tidy, and remove e2e
* test fixes
* fix vai group by
* Fix for grouping (secrets --> group by namespace --> pss --> table is incorrectly grouped but toggle is correct
* fix warning
* fix clone/yaml, fix default/system pss
* don't fetch projects, it wipes out header. this means in upstream we won't show project names for pss downstream
* fix lint
* fix ts complain
* Tweak column tooltips
* Add cypress logs for failing tests
* pipe in `inStore`
* tweaks to cypress logs process
- better name
- log http requests
- only create logs if run failed
* Secret selector improvements and test fixes
- don't cache or watch secrets if we're showing multiple selectors on a page
- ensure we classify secrets (make it into an instance of a model)
---------
Co-authored-by: Mo Mesgin <mmesgin@Mos-M2-MacBook-Pro.local>
Co-authored-by: momesgin <mo.mesgin@suse.com>
- Fix issue with undefined routes
- Fix issue with the ResourceDetailDrawer closing when opened in harvester.
- Fixed an issue where the link back to the list page was wrong.
* update AppModal, PromptModal and focusTrap to use only the watcher based focus trap and wire in required props for prompt modals + add unit test for current prompt modals display assertion + minor tweaks to current prompt modals so that they work fine on unit tests
* update PR with recommended changes
* fix lint issue
* push to retry pipelines
* remove unit test variable from promptModal
* remove prop not needed - autoTriggerFocusTrapWatcher
This composable is intended to be used for any feature flags that we may need to specify for maintaining backwards compatibility with previous versions of Rancher Shell. At the moment, this composable contains a feature flag for toggling the new dropdown menu.
Signed-off-by: Phillip Rak <rak.phillip@gmail.com>
* working on focus trap composable
* working on slide in panel refactor
* add change so that we dont have a change on the component diff
* fix slidein extension details panel key nav
* fine tune cluster badge trigger btn
* finish work on extensions page
* fix lint errors
* address pr comments
* fix problems of propagation
* update return focus for some modals in the extensions main screen
* remove dead code + fix focus selector return for add extensions repo and developer install modals
The `useStore` composable was implemented for Vue2 because vuex did not provide anything for the composition api. Now that we have migrated to Vue3, we have `useStore` exposed to us via Vuex.
Signed-off-by: Phillip Rak <rak.phillip@gmail.com>
Rewrote `compact-input.ts` and `labeled-form-element.ts` mixins as composables to address TypeScript issues when using mixins with `defineComponent`. The new composables are written to adhere to the conventions and best practices [^1] as best as possible, taking into consideration what's available to us in Vue 2.7.14.
Moving to composables positions us for a smoother Vue 3 migration.
[^1]: https://vuejs.org/guide/reusability/composables.html#conventions-and-best-practices
Signed-off-by: Phillip Rak <rak.phillip@gmail.com>
Richard Cox
codyrancher
Alexandre Alves
Phillip Rak
Alexandre Alves