redhat-developer / redhat-developer/mapt
Error if not passing param `conn-details-output`
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 24
- Forks
- 36
- Avg merge
- 6d 13h
- Merged PRs (30d)
- 8
Description
Based on https://github.com/redhat-developer/mapt/pull/262#issuecomment-2242895881 it is possible mapt ends up failing due to missing param.
In this case param should be mandatory, check if that should be the case if host will be executed as gh self-hosted runner
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 with the discussion in pull request 262 and trace how the conn-details-output parameter is handled in the mapt command. Check the path where the host is executed as a GitHub self-hosted runner. Done means the parameter behavior is defined and the missing-parameter failure is handled consistently.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- devops
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100