redhat-developer / redhat-developer/mapt
[enhancement] Do we want / need ssh creds whe running mapt as ci/cd runner
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 24
- Forks
- 36
- Avg merge
- 6d 13h
- Merged PRs (30d)
- 8
Description
When we run mapt to include the target as a ci/cd runner (self hosted runner on gh for the moment, persistent worker for cirrus in the future) do we really need the ssh information? as typically actions executed on the target are driven by the ci/cd system client?
Still maybe relevant to debug purposes?
WDYT @anjannath ??
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
The issue names no files, tests, or entry points. Start by tracing how mapt provisions self-hosted GitHub Actions runner targets and how SSH information is consumed; done means reaching a documented decision about whether those credentials are needed, including their debugging use.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github-actions, go
- Domain
- ci-cd, devops, security
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100