Platforms Operations/APIs: Difference between revisions
Jump to navigation
Jump to search
(Initial info) |
(fixed wiki markup) |
||
| Line 12: | Line 12: | ||
== Project phases == | == Project phases == | ||
# Establish list of APIs provided within Platform Operations | |||
# Establish authentication/permissions models used, to see what commonality they share | |||
# Decide on an API format suitable for describing the various APIs | |||
# Provide an ingestion service that allows internal service providers within the team to submit API definitions | |||
# Look into aligning auth/permissions models to provide a single command line and set of platform libraries | |||
== Known APIs == | == Known APIs == | ||
This is currently being captured in https://public.etherpad-mozilla.org/p/plat-ops-apis | This is currently being captured in https://public.etherpad-mozilla.org/p/plat-ops-apis | ||
Revision as of 17:50, 20 June 2016
Platform Operations provides services for developers. Most of these services are exposed via APIs.
It is our intention to provide a uniform view of the APIs we offer as an organisation, much like AWS provides a uniform command line client, platform libraries and web based docs, driven from schemas which are published when services are deployed.
| IRC channel | #plat-ops-apis |
| Mailing list | <to be created shortly> |
Project phases
- Establish list of APIs provided within Platform Operations
- Establish authentication/permissions models used, to see what commonality they share
- Decide on an API format suitable for describing the various APIs
- Provide an ingestion service that allows internal service providers within the team to submit API definitions
- Look into aligning auth/permissions models to provide a single command line and set of platform libraries
Known APIs
This is currently being captured in https://public.etherpad-mozilla.org/p/plat-ops-apis