also renames a the commands to start with cmd followed by the args. this
is an attempt to order the commands in a slightly more autocomplete friendly
way.
* feat(ui/DWP): added searchable dropdown for tag key and values for selected bucket
* feat(DWP-targets): key-value tags are associated with selected bucket
* fix(predicates/action): reordered actions so that actions alphabetical and thunks are at the bottom of the page
* feat(DWP-dropdown): made suggested PR changes
* fix(DWP-dropdown): added filter predicate to tagKeys query
* feat(ui/DWP): added searchable dropdown for tag key and values for selected bucket
* feat(DWP-targets): key-value tags are associated with selected bucket
* fix(predicates/action): reordered actions so that actions alphabetical and thunks are at the bottom of the page
* feat(DWP-dropdown): made suggested PR changes
* fix(DWP-dropdown): added filter predicate to tagKeys query
* first steps to predicate action tests
* fix(dwp-dropdown): added action tests for thunk actions
* fix(predicates.test): removed unnecessary store and redux logic from test
A KV store may optionally implement a key predicate
function to filter on keys, which may reduce memory and CPU usage.
Expected user resource mapping improvements for a single user:
Before:
3813719 ns/op 4170142 B/op 33 allocs/op
After:
316869 ns/op 816 B/op 15 allocs/op
* fix(ui): Remove add member flow and users redux state
* fix(getResourcesStatus): added tests to getresources function to ensure stability
* Refactor getResourcesStatus and testing
one thing to note here is that new endpoint was created. there was no
endpoint for setting an initial password that worked. The existin endpoint
was a bit messy and coupled across multiple routes. Having multiple auth
schemes proved incredibly taxing to write against.
* Removed an unused function as cleanup.
* Users without true system buckets won't have fake buckets returned if they don't specify their org in the request, but this shouldn't break tasks.