Bug #14546
closed
No ability to restrict *_external_variables with search anymore
Added by Sander Hoentjen about 8 years ago.
Updated almost 6 years ago.
Category:
Users, Roles and Permissions
|
|
Description
Since Foreman 1.10 it is not possible to restrict Resource="Lookup key" with search anymore. The page to edit says:
"Selected resource type does not support granular filtering, therefore you can't configure granularity"
In Foreman 1.9 this was working fine.
- Related to Refactor #10832: Make LookupKey an STI for puppet and variable keys added
- Related to Bug #14535: /api/smart_class_parameters needs administrator permissions added
- Subject changed from No abilitie to restrict *_external_variables with search anymore to No ability to restrict *_external_variables with search anymore
- Category set to Users, Roles and Permissions
Looking in more detail, this might be more closely related to #14535 than I thought. It's likely that having the permission point to LookupKey rather than PuppetclassLookupKey means the granularity? check is failing, as LookupKey itself has no search function.
- Status changed from New to Ready For Testing
- Assignee set to Ori Rabin
- Pull request https://github.com/theforeman/foreman/pull/3530 added
- Status changed from Ready For Testing to Closed
- % Done changed from 0 to 100
- translation missing: en.field_release set to 136
- Related to Bug #15445: Filter not working for permission: edit_params from resource: parameter added
- Bugzilla link set to 1360191
Also available in: Atom
PDF
Updated by 
Updated by 
Updated by 
Updated by