Allow specifying minor versions of tools or automatic selection of the latest
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 35/100
- Issue type
- Feature
- Clarity
- Mostly clear
- Activity status
- Stale
- Tech stack
- typescript
Research direction
Start by locating the configuration handling for the proposed TrivyVersion and TrivyUseLatestMinor settings, then trace how bundled tool versions are selected. Done should support an explicit minor-version policy or latest-minor selection while preserving the existing major-version compatibility boundary.
Written by the indexing model from the issue text.
Description
Feature Request: Allow us to specify minor version of the underlying tools
Quite often there are warnings and issues with the tools bundled with guardian/SDO.
I understand the need to somewhat control versions in other to know what "works" from an integration perspective, and freely allowing major version changes may be quite troublesome.
That said if we could have an override that allowed us to either specify a version to use, say TrivyVersion = 0.68.0 (allowing us to upgrade to all minor versions before 1.00 for instance), or alternatively a "TrivyUseLatestMinor=true" that would help alleviate the pains we have with the warnings/errors that are surfaced in the included tools and not directly by SDO.
- Dominant language
- TypeScript
- Stars
- 86
- Forks
- 22
- PR merge metrics
- No merged PRs in 30d
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.
More from microsoft/security-devops-azdevops
-
Difficulty 1/5 Under an hour Newbie friendliness 68/100
-
area:task area:tools status:waiting-on-author type:docs type:question
microsoft/security-devops-azdevops#169 · 1 comment · 1 assignee ·
-
Which Defender CLI binary should be used in CI/CD pipelines — `aka.ms` or the DevOps CDN endpoint? Open
Difficulty 5/5 Over a week Newbie friendliness 35/100
microsoft/security-devops-azdevops#166 · 2 comments · 1 reaction ·
-
area:task area:tools status:team-review type:feature
microsoft/security-devops-azdevops#164 · 2 reactions · 2 assignees ·
-
area:task area:tools status:team-review type:docs type:feature
microsoft/security-devops-azdevops#163 · 17 comments · 1 assignee ·
All issues in microsoft/security-devops-azdevops
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
copse-dev/agent-pane#2953 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
Eynzof/Hermes-CN-Desktop#610 ·
-
bug clawsweeper:linked-pr-open clawsweeper:needs-live-repro clawsweeper:no-new-fix-pr impact:message-loss issue-rating: 🐚 platinum hermit P2 regression
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
-
enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
-
calcite-components needs triage refactor
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
Esri/calcite-design-system#15203 ·