GDATASoftwareAG / GDATASoftwareAG/vaas-helm
forFile and forUrl are not interrupted if scan nodes are updated
Open
Nobody has claimed this yet.
enhancement
- Dominant language
- Go Template
- Stars
- 2
- Forks
- 1
- PR merge metrics
- No merged PRs in 30d
Description
If scan nodes are updated, existing scans and new requests should not be impacted - it should be seamless.
Acceptance criteria:
- New requests are not impacted by scan node updates
- Long requests (< grace peroid) are not impacted by scan node updates
Test scenarios:
- Repeatedly scan a small files (< 1 MB), 8 clients
- Repeatedly scan a big file (scan duration > 20s), 1 client
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 the forFile and forUrl entry points and reproduce the listed small-file and long-request scenarios while scan nodes are updated. Done means new requests and requests shorter than the grace period continue without interruption during those updates.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- helm
- Domain
- infrastructure
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100