nextcloud / nextcloud/documentation
Add coverage in [Primary Storage - Object Storage - S3] "Deleted files continue to exist in bucket"
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 628
- Forks
- 2.5k
- Avg merge
- 2d 11h
- Merged PRs (30d)
- 135
Description
Several open issues in nextcloud/server overlap with this matter:
-
see those Issues for material/coverage ideas
-
See docs for providers such as: AWS, Backblaze[^backblaze], etc.
[^backblaze]: "Buckets in Backblaze B2 are versioned by default. Because buckets are versioned, when a file is deleted by referencing the name, only the most recent version of that file is deleted and older versions of the file continue to exist in the bucket." -- https://www.backblaze.com/apidocs/introduction-to-the-s3-compatible-api ("Differences from AWS S3")
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 overlapping nextcloud/server issues and the AWS and Backblaze S3 provider documentation referenced in the issue. Done means adding coverage for deleted files that remain as older object versions; no target documentation file or test is identified.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- aws
- Domain
- cloud, documentation
- Issue type
- Documentation
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 38/100