Open git-hyagi opened 1 month ago
I would maybe allow plugin writers to create custom aliases or pass their own arguments to the function.
We should look into this technology: https://rsinger86.github.io/drf-access-policy/policy_reuse/#access-policy-re-use
Maybe we add something like has_related_field_obj_permission:<fieldname>;<permission>
.
I believe we only have one string to pass around.
Is your feature request related to a problem? Please describe. The
has_repo_or_repo_ver_param_model_or_obj_perms
function verifies onlyrepository
orrepository_version
as parameters. In pulp-container image build machinery, instead ofrepository_version
, we are planning to add a field calledbuild_context
(where users would be passing a filerepository_version
href to be used as the build context of the image build process).Describe the solution you'd like Add support in
has_repo_or_repo_ver_param_model_or_obj_perms
to also validate the permissions based onbuild_context
.Describe alternatives you've considered We thought about creating a new access condition function in pulp-container, but, to avoid the code repetition, maybe it would be better to keep using the pulpcore
has_repo_or_repo_ver_param_model_or_obj_perms
. To workaround this "limitation" we are having to do something like: