redhat-developer / redhat-developer/mapt
[self-hosted] remove self hosted runner when running `mapt destroy`
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 24
- Forks
- 36
- Avg merge
- 6d 13h
- Merged PRs (30d)
- 8
Description
Currently when the self hosted runner machine is deleted on the cloud provider, its marked as offline on the runners page, we should instead remove the runner from github before deleting the cloud resources, as there is a limit to the number of runners that can be added
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 at the implementation of mapt destroy and trace how self-hosted runners and cloud resources are deleted. Identify the GitHub runner removal path and the resource teardown entry point; done means the runner is removed from GitHub before its cloud machine and related resources are deleted.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github, go
- Domain
- ci-cd, cloud, devops
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100