mandiant / mandiant/VM-Packages
Add consoleApp to METAPACKAGE issue template + script
Open
Nobody has claimed this yet.
:gem: enhancement
:runner: CI
- Dominant language
- PowerShell
- Stars
- 246
- Forks
- 98
- Avg merge
- 9h 30m
- Merged PRs (30d)
- 7
Description
### Details
We have the option to specify if a tool is a console application for packages installed from a URL, but not for metapackages. It should be added as well, which implies modifying the METAPACKAGE_TEMPLATE in our script and possibly adapting the automation.
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
Locate the script containing METAPACKAGE_TEMPLATE and compare it with the existing URL-package consoleApp handling. Trace the related automation to determine where metapackage metadata is generated or consumed. Done means metapackages can specify consoleApp consistently and the affected automation still works.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- powershell
- Domain
- tooling
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100