Add a configuration option to allow/deny downloading the closure
Open
Nobody has claimed this yet.
feature
- Dominant language
- PLpgSQL
- Stars
- 1.6k
- Forks
- 358
- Avg merge
- 20h 30m
- Merged PRs (30d)
- 27
Description
I'm using hydra to build some projects that should be visible to everyone, but not everyone should be allowed to download every project, because some projects contain proprietary/confidential data. Thus, it'd be nice to be able to configure who may download built closures.
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
The issue names no files, tests, or entry points. Start by locating Hydra’s closure-download path and existing access-control configuration, then determine how permissions should be configured and enforced. Done means the behavior is covered for both allowed and denied downloads.
Written by the indexing model from the issue text.
Assessment
- Domain
- authorization, security
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100