as a Dataverse administrator who has migrated to AWS, I'd like to disable the "file" store
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 1.1k
- Forks
- 564
- Avg merge
- 2d 2h
- Merged PRs (30d)
- 29
Description
IIRC the storage selection at time of Dataverse collection creation is presented only to admin users. The "storage" selection doesn't present for me in the "create Dataverse (collection)" page, but for safety and cleanliness I might like to disable/remove the formerly default "file" store.
Is this as simple as removing
-Ddataverse.files.file.type=file
-Ddataverse.files.file.label=file
-Ddataverse.files.file.directory=/path
from domain.xml? I'd assume I'd want to verify no storageidentifiers use file:// but am wondering what else might break.
If this is unknown I'll test and report back. If IQSS finds it worthwhile I can submit a documentation PR.
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 storage settings in domain.xml and checking whether any storageidentifiers use the file:// scheme. Verify what breaks when the file store properties are removed, then document the supported removal procedure, required checks, and any migration or cleanup concerns.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- aws, java
- Domain
- cloud, infrastructure
- Issue type
- Documentation
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100