awslabs / awslabs/simple-code-scanning-pipeline
Allow support for bringing your own scan_results_bucket from home
Open
- Dominant language
- TypeScript
- Stars
- 19
- Forks
- 3
- PR merge metrics
- No merged PRs in 30d
Description
If we allow users to specify where their results should be sent, this can allow for a central bucket that contains all scan results for all code on a given project.
Feature request from @raduraul
Contributor guide
Research direction
No file, test, or entry point is named in the issue. Start by locating the existing scan_results_bucket configuration and its result-upload path; done means users can provide their own destination and all scan results for a project can be collected in that bucket.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- aws, typescript
- Domain
- cloud
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100