redhat-developer / redhat-developer/mapt
[Enhancement] Check machines type requirements based on other target specs
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 24
- Forks
- 36
- Avg merge
- 6d 13h
- Merged PRs (30d)
- 8
Description
Originally posted by @anjannath in https://github.com/redhat-developer/mapt/pull/309#discussion_r1836644605
When we apply a ProfileSNC we know it should require a machine with nested virt enable.
Right now this is done at cmd level but it should be moved to acion level
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 by tracing the current command-level handling of nested virtualization requirements for ProfileSNC, then locate the corresponding action-level logic and how other target specifications are applied. Done means the machine requirement is derived and enforced at the action level instead of the command level.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- devops, infrastructure
- Issue type
- Refactor
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100