Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add config to lock video ACLs to their series #1305

Open
wants to merge 6 commits into
base: next
Choose a base branch
from

Conversation

owi92
Copy link
Member

@owi92 owi92 commented Dec 16, 2024

This will disable ACL editing for the uploader and the ACL UI when the video is part of a series.
Uploaded videos will then adopt the ACL of that series.

This needs to be configured with lock_acl_to_series, the default for this is false.

Closes #1006

@owi92 owi92 added the changelog:user User facing changes label Dec 16, 2024
@owi92 owi92 changed the base branch from main to next December 16, 2024 11:25

This comment has been minimized.

@github-actions github-actions bot temporarily deployed to test-deployment-pr1305 December 16, 2024 11:33 Destroyed
@github-actions github-actions bot added the status:conflicts This PR has conflicts that need to be resolved label Dec 16, 2024
Copy link

This pull request has conflicts ☹
Please resolve those so we can review the pull request.
Thanks.

With this enabled, event ACLs can't be edited and will generally
be determined by their series.
The search series view knows about read and write
roles, but they are hex encoded. In order to display
the correct ACL including labels for user names and groups,
they need to be decoded and processed into the right data
structure first. Fortunately, there are already functions
for both decoding and processing/formatting ACLs.
The backend serves these ACLs as arrays of objects holding
role, actions and info values. The frontend ACL editor
needs this as a map with role as key and the other two props
as values.

This translation of array to map was already being done
in a few different places and I was about to add another
instance. At that point I think it's ok to just put this
logic in a reusable function.
And then also disable ACL editing and attachment.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
changelog:user User facing changes
Projects
None yet
Development

Successfully merging this pull request may close these issues.

The visibility selection to control ACL in the uploader should be configurable
1 participant