Dupe'd Migrant: Pitch: Cloud.gov API
Shape Up Pitch
Problem:
We need to be able to provide services independent of Cloud Foundry. This is critical for expanding our reach and impact. It is also critical to ensure a future where Cloud Foundry is not the only compute option.
Appetite
How much time we want to spend and how that constrains the solution
-
[We have appetite for 2 weeks] -
[we have appetite for 12 weeks]
Solution
Initially, we need to lay the ground work by building a stateful API. This will require:
- An API endpoint application
- A persistent database
- Integration with UAA for authentication and authorization
The intent is not build the entire API but to implement a few features end to end to ensure everything is in place. The scope of these features can be determined later. Examples could include:
- Authentication
- Viewing available services (marketplace)
- Ability to provision a new service instance outside of Cloud Foundry (probably too ambitious for this quarter).
Rabbit Holes
Details about the solution worth calling out to avoid problems
- Trying to implement too much in this quarter. Focus on getting end to end authentication and authorization working, perhaps with a query to an existing Cloud Foundry API (example: listing orgs).
No-Gos
The intent is not to be build a full featured API or CLI. The API should be the priority with the CLI slated for future development.