*What*
Document the required & optional bits for a service APB.
The target for this document is a an APB developer that want's the provisioned service to be consumable as a 'Mobile Service'
(see terminology https://github.com/aerogear/mobile-core/blob/master/docs/architecture/architecture-overview.adoc#terminology)
*Why*
So an APB developer knows what is required to be able to integrate with the Mobile CLI and SDKs.
Also, so an APB developer knows what optional integrations & configuration there are e.g. Prometheus metrics endpoint via annotations
*How*
This list is not exhaustive, but a starting point. There may be other requirements and optional bit bits that would benefit from being documented.
Required
* Split of Configmap & Secret for any config/keys to be exposed to Mobile apps vs. 'administrative' secrets. See https://github.com/aerogear/proposals/blob/master/apbs/create-secret-and-configmap-during-provision.md
Optional
* Metrics endpoint for Prometheus. See https://github.com/aerogearcatalog/metrics-apb/blob/master/roles/provision-metrics-apb/templates/prometheus-config-map.yml.j2
* Metrics dashboard for Grafana. See https://github.com/aerogearcatalog/metrics-apb#how-auto-discovery-of-services-work |
|
