Confirmed users
142
edits
Platforms Operations/APIs: Difference between revisions
Initial info
(An overview of all API collections provided by Platform Operations) |
(Initial info) |
||
| Line 1: | Line 1: | ||
API | 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. | |||
{| class="wikitable sortable" | |||
|- | |||
| '''IRC channel''' || #plat-ops-apis | |||
|- | |||
| '''Mailing list''' || <to be created shortly> | |||
|} | |||
== Project phases == | |||
1) Establish list of APIs provided within Platform Operations | |||
2) Establish authentication/permissions models used, to see what commonality they share | |||
3) Decide on an API format suitable for describing the various APIs | |||
4) Provide an ingestion service that allows internal service providers within the team to submit API definitions | |||
5) 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 | |||