DEFAULT_PERMISSION_CLASSES
, while still being able to take advantage of the pulp systemsIn an ideal world we would be able to define our own DEFAULT_PERMISSION_CLASSES
, which would load a custom access policy like this:
class GalaxyAccessPolicyBase(AccessPolicyFromDB):
def get_policy_statements(self, view):
viewset_name = get_view_urlpattern(view)
if viewset_name in CUSTOM_STATEMENTS:
return CUSTOM_STATEMENTS[viewset_name]
return view.DEFAULT_ACCESS_POLICY
This would allow us to define override access policies for other viewsets without messy database migrations, create customized condition_functions and take advantage of the default pulp access policies.
This comes with some challenges because it breaks creation_hooks
, which we don't currently use (but might start using in the future) and default role definitions.
AutoAddObjMixin
to use the DEFAULT_PERMISSION_CLASSES
to load access policies for permission assignmentor
or
By clicking below, you agree to our terms of service.
New to HackMD? Sign up
Syntax | Example | Reference | |
---|---|---|---|
# Header | Header | 基本排版 | |
- Unordered List |
|
||
1. Ordered List |
|
||
- [ ] Todo List |
|
||
> Blockquote | Blockquote |
||
**Bold font** | Bold font | ||
*Italics font* | Italics font | ||
~~Strikethrough~~ | |||
19^th^ | 19th | ||
H~2~O | H2O | ||
++Inserted text++ | Inserted text | ||
==Marked text== | Marked text | ||
[link text](https:// "title") | Link | ||
 | Image | ||
`Code` | Code |
在筆記中貼入程式碼 | |
```javascript var i = 0; ``` |
|
||
:smile: | ![]() |
Emoji list | |
{%youtube youtube_id %} | Externals | ||
$L^aT_eX$ | LaTeX | ||
:::info This is a alert area. ::: |
This is a alert area. |
On a scale of 0-10, how likely is it that you would recommend HackMD to your friends, family or business associates?
Please give us some advice and help us improve HackMD.
Syncing