mkdevops-se / mkdevops-se/hq.mkdevops.se
Add 2nd key for me?
Open
Nobody has claimed this yet.
- Dominant language
- Jinja
- Stars
- 1
- Forks
- 1
- PR merge metrics
- No merged PRs in 30d
Description
ssh-rsa AAAAB3NzaC1yc2EAAAADAQABAAABAQD3Yq5WL/H+uj5EBjK5moxgfzzrqbhlOL23+oF2WuzjCaM0CTMpWQaIupS/1ejt+4KrCN73L62wrzs82Dzz+7EfhLLXVYC8Yw1a4aUzOkITwnLiHrYH+2hGfgnexF4GvWofilTh54SUtxSjqYRuWqjIuvoIl+81q4R9mx2gLsoENcFGFz3YnKr9ZwIx7Fs6xw2ASI7UNCsNkebYM6yFf8xBHvUOC+mD5HIrCofs2pPu+ojldITfI4++zB4BxVvjFcHofTdDQdfA9lRQ9TztFun4oZ/qH3rIoOtslJmNfbl8zgmR9aUu82vVIJeULV36iRVBi4h1sMeAfF2oasmBCjvV tempmablo
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
No file or test is named. Inspect the repository's Ansible bootstrapping entry points to find where SSH keys are configured, then verify that the supplied second key is provisioned for the intended account without disrupting the existing key.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- ansible
- Domain
- infrastructure
- Issue type
- Feature
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100