As a user, I can protect content in S3
Open
Nobody has claimed this yet.
Feature
- Dominant language
- Python
- Stars
- 598
- Forks
- 168
- Avg merge
- 1d 4h
- Merged PRs (30d)
- 86
Description
Author: daviddavis (daviddavis)
Redmine Issue: 4539, https://pulp.plan.io/issues/4539
I know there are some options to lock down content in django-storages. We need to confirm that they work.
Also, we need to explore use cases such as having some content protected and other content not protected.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reviewing the referenced django-storages options for protecting S3 content and the existing pulpcore storage configuration. Investigate the stated use cases for mixing protected and unprotected content. Done means the supported locking behavior and mixed-access requirements are resolved and captured in an implementation plan.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- backend, cloud
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100