Avoid isPrivate as a Blob Property for new blobs
Open
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 1.8k
- Forks
- 298
- Avg merge
- 21h 43m
- Merged PRs (30d)
- 9
Description
With container support, blob privacy is handled at the container level. The blob level isPrivate property which is part of `BlobProperties` should be avoided for newly created blobs. This issue is created to figure out the best way to do this.
Contributor guide
No contributing guide indexed for this repository
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 with BlobProperties and the container and blob creation paths, focusing on how isPrivate is currently assigned for new blobs. Compare that behavior with container-level privacy, then document or implement the agreed approach for avoiding the blob-level property.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- distributed-systems
- Issue type
- Refactor
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100