redhat-developer / redhat-developer/mapt
[Feature] Ability to expose the SSH credentials before waiting OCP readiness
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 24
- Forks
- 36
- Avg merge
- 6d 13h
- Merged PRs (30d)
- 8
Description
Currently, mapt generates the secrets at the end of the deployment.
However, if the step main-ocp-readiness-aos-cmd never completes (because of a bug in the systemd launcher), one cannot access the cluster to troubleshoot it.
Would be nice if mapt could dump:
- the hostname
- the ssh private key
- (the username)
at the end of the main-ssh-readiness-aos-cmd step.
Workaround is to run with the --debug flag to see the private key, and get the instance public IP from AWS console.
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 deployment flow around the main-ssh-readiness-aos-cmd and main-ocp-readiness-aos-cmd steps. Check where the hostname, SSH private key, and username are generated or exposed, then verify that they are available immediately after SSH readiness even if OCP readiness does not complete.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- aws, go
- Domain
- cli, cloud, infrastructure
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100