Fix kv secret access bug (#13872)

* Fix kv secret access bug

- Set permissions state when call is successful

* Added changelog
This commit is contained in:
Arnav Palnitkar 2022-02-03 01:46:03 +05:30 committed by GitHub
parent 34630f6557
commit 91e5877d4a
No known key found for this signature in database
GPG key ID: 4AEE18F83AFDEB23
2 changed files with 6 additions and 1 deletions

3
changelog/13872.txt Normal file
View file

@ -0,0 +1,3 @@
```release-note:bug
ui: Fix kv engine access bug
```

View file

@ -10,7 +10,8 @@ const SUPPORTED_BACKENDS = supportedSecretBackends();
export default Route.extend({ export default Route.extend({
templateName: 'vault/cluster/secrets/backend/list', templateName: 'vault/cluster/secrets/backend/list',
pathHelp: service('path-help'), pathHelp: service('path-help'),
noMetadataPermissions: false, // By default assume user doesn't have permissions
noMetadataPermissions: true,
queryParams: { queryParams: {
page: { page: {
refreshModel: true, refreshModel: true,
@ -105,6 +106,7 @@ export default Route.extend({
pageFilter: params.pageFilter, pageFilter: params.pageFilter,
}) })
.then((model) => { .then((model) => {
this.set('noMetadataPermissions', false);
this.set('has404', false); this.set('has404', false);
return model; return model;
}) })