quickwit-oss / quickwit-oss/quickwit
How do you recommend securing access to a quickwit node?
Open
Nobody has claimed this yet.
enhancement
- Dominant language
- Rust
- Stars
- 11.7k
- Forks
- 597
- Avg merge
- 2d 22h
- Merged PRs (30d)
- 37
Description
Question asked on twitter: https://twitter.com/castconstruct/status/1596558474355560448
Maybe @kstaken or @clemcvlcs have an idea of how to do it correctly.
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
Begin with the linked Twitter question and the security question in this issue; no repository file, test, or entry point is named. Done would require an agreed, project-specific recommendation for securing access to a Quickwit node, documented for users.
Written by the indexing model from the issue text.
Assessment
- Domain
- security
- Issue type
- Documentation
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100