cloudfoundry / cloudfoundry/go-uaa
Curl non-UAA hosts w/UAA context
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 13
- Forks
- 25
- Avg merge
- 1d 15h
- Merged PRs (30d)
- 8
Description
See https://github.com/cloudfoundry-incubator/uaa-cli/issues/62
Assuming this should be implemented it seems like go-uaa's curl function should support external hosts versus duplicating a bunch of the transport logic in the CLI.
This Curl function could be backwards compatible based off if the passed in url contains a host.
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 reading the go-uaa Curl function and the linked uaa-cli issue 62. Compare how the CLI currently handles external hosts and how go-uaa handles URLs with and without a host. Done means Curl supports non-UAA hosts with UAA context without breaking existing URL behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- api
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100