Don't filter out read role.

This commit is contained in:
Bill Nottingham 2018-07-03 14:00:38 -04:00
parent 77815c20a4
commit e271a69efb
3 changed files with 3 additions and 5 deletions

View File

@ -25,9 +25,7 @@ export default ['$rootScope', '$scope', 'GetBasePath', 'Rest', '$q', 'Wait', 'Pr
// the object permissions are being added to
scope.object = scope.resourceData.data;
// array for all possible roles for the object
scope.roles = _.omit(scope.object.summary_fields.object_roles, (key) => {
return key.name === 'Read';
});
scope.roles = scope.object.summary_fields.object_roles;
// TODO: get working with api
// array w roles and descriptions for key

View File

@ -67,7 +67,7 @@
<div class="AddPermissions-keyPane"
ng-show="showKeyPane">
<div class="AddPermissions-keyRow"
ng-repeat="key in roleKey | filter:{name: '!Read'}">
ng-repeat="key in roleKey">
<div class="AddPermissions-keyName">
{{ key.name }}
</div>

View File

@ -78,7 +78,7 @@ function(scope, $state, i18n, CreateSelect2, Rest, $q, Wait, ProcessErrors) {
// aggregate name/descriptions for each available role, based on resource type
// reasoning:
function aggregateKey(item, type){
_.merge(scope.keys[type], _.omit(item.summary_fields.object_roles, 'read_role'));
_.merge(scope.keys[type], item.summary_fields.object_roles);
}
scope.closeModal = function() {