consul/ui/packages/consul-ui/tests/acceptance/dc/kvs
John Cowen cf638ee551
ui: Always show main navigation Key/Value link (#10916)
* ui: Ignore response from API for KV permissions

Currently there is no way for us to use our HTTP authorization API
endpoint to tell us whether a user has access to any KVs (including the
case where a user may not have access to the root KV store, but do have
access to a sub item)

This is a little weird still as in the above case the user would click
on this link and still get a 403 for the root, and then have to manually
type in the URL for the KV they do have access to.

Despite this we think this change makes sense as at least something about KV is
visible in the main navigation.

Once we have the ability to know if any KVs are accessible, we can add
this guard back in.

We'd initially just removed the logic around the button, but then
noticed there may be further related KV issues due to the nested nature
of KVs so we finally decided on simply ignoring the responses from the
HTTP API, essentially reverting the KV area back to being a thin client.
This means when things are revisited in the backend we can undo this
easily change in one place.

* Move acceptance tests to use ACLs perms instead of KV ones
2021-09-22 18:23:59 +01:00
..
sessions ui: Adds Partitions to the HTTP layer (#10447) 2021-09-15 18:09:55 +01:00
create.feature ui: Partitions Application Layer (#11017) 2021-09-15 19:50:11 +01:00
delete.feature ui: Move to Workspaced Structure (#8994) 2020-10-21 15:23:16 +01:00
edit.feature ui: Restrict the viewing/editing of certain UI elements based on the users ACLs (#9687) 2021-02-19 16:42:16 +00:00
index.feature ui: Always show main navigation Key/Value link (#10916) 2021-09-22 18:23:59 +01:00
list-order.feature ui: Move to Workspaced Structure (#8994) 2020-10-21 15:23:16 +01:00
trailing-slash.feature ui: Move to Workspaced Structure (#8994) 2020-10-21 15:23:16 +01:00
update.feature ui: Partitions Application Layer (#11017) 2021-09-15 19:50:11 +01:00