Support for Drupal 7 is ending on 5 January 2025—it’s time to migrate to Drupal 10! Learn about the many benefits of Drupal 10 and find migration tools in our resource center.Problem/Motivation
On a new project the client gave us an API client with just read permissions. This might sound not like a problem, but for example the subscriptions causes update requests to brightcove, which causes fatals if the permissions aren't there.
Proposed resolution
Provide a way to flag API clients in Drupal to be marked as read only and take that into account when deleting/updating videos and playlists
Remaining tasks
- Determine/Discuss whether this is really a good idea
- Determine the scope, aka. did we found all places code might want to update remote data
User interface changes
API changes
Data model changes
| Comment | File | Size | Author |
|---|---|---|---|
| #4 | brightcove-allow_read_only-2894717-4.patch | 4.52 KB | IJsbrandy |
| #3 | brightcove-allow_read_only-2894717-3.patch | 3.98 KB | merauluka |
Comments
Comment #2
dawehnerComment #3
merauluka CreditAttribution: merauluka at Mediacurrent commentedRerolled this patch against the latest copy of dev since the patch in #2 no longer applied cleanly.
Comment #4
IJsbrandy CreditAttribution: IJsbrandy at Betawerk commentedAlthough you can set the readonly value manually a checkbox field is missing in the client api form to set the readonly value. This is now included in the patch.
Comment #5
yce CreditAttribution: yce at Pronovix for BrightCove commentedHi,
For me it just seems like a workaround, the permission checks is not yet implemented in this module.
I would rather not add this read only functionality, instead the permission handling should be implemented.
Comment #6
yce CreditAttribution: yce at Pronovix for BrightCove commentedComment #7
yce CreditAttribution: yce at Pronovix for BrightCove commented