l3montree-dev / l3montree-dev/devguard
Add Deployment(s) to an Artifact
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 161
- Forks
- 43
- Avg merge
- 1d 8h
- Merged PRs (30d)
- 37
Description
Is your feature request related to a problem? Please describe.
I would like to understand where a vulnerable artefact is deployed within my organisation.
Describe the solution you'd like
Add a 0-n deployment field to an artifact (version?) which allows to track on which server, cluster, vm and so on the current artefact / version is deployed.
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 locating the artifact and artifact-version models and the API entry points that expose them. Define how zero or more deployments relate to the current artifact or version, including server, cluster, or VM targets. Done means the deployment information can be stored and retrieved for a vulnerable artifact so its deployment locations are traceable.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- backend, security
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100