Creating SOCKS session on OCI bastion fails on Windows
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 669
- Forks
- 236
- Avg merge
- 1m
- Merged PRs (30d)
- 4
Description
--key-details json parameter is not recognized. It works fine on MacOS.
Usage: oci.exe bastion session create-session-create-dynamic-port-forwarding-session-target-resource-details [OPTIONS] Error: Got unexpected extra argument (publicKeyContent:\ssh-rsa AAAAB3NzaC1yc2EAAAADAQABAAABgQCdo2k3RELR3EMjq5fSNcrN+YjAgTNrpDq3bKzYzznCwACxfknSBkU0yNRNgPL3cWTQa3hiOB4faS1j59CClIRAMUG2BEO9iRKnq9ZgQ8vfDZWY...
Json parameter format is correct though.
It would be better to pass a public key file like other connection modes (managed-ssh and port-forwarding)
Contributor guide
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 reproducing the OCI bastion dynamic port-forwarding session command on Windows, focusing on the --key-details option and its JSON parsing. Review the command's option handling; done means the supplied public-key JSON is accepted and the session can be created, or a public key file is supported consistently with managed-ssh and port-forwarding.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- cli, cloud, infrastructure
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100