Open ryanj opened 9 years ago
How about moving /changes
to /container/changes
?
Sounds good. I'm working out API implementation here: https://github.com/ryanj/1k-commander
Up next:
Sounds like we may be sending PNGs instead of text-based "claims". An admin review queue may be needed.
We can't store PNG data in the ENV. PNG images will be destroyed when the container is deleted.
Mobile / Feedhenry team is going to own the data validation UI. They'll post the cleaned result directly to a container. All data will be lost when/if the container is destroyed.
mocking out ideas for mobile integration endpoints...
GET /containers
This should return the full list of known demo containers. A kubernetes label can be used to track these instances and to make sure our viz apps are excluded from the result:
...
WS GET /changes
Listen to a websocket stream of status updates
GET /container/id
should return a single item
PUT /container/id
Set ENV keys for this container in the querystring to claim (or steal):
DELETE /container/id
Kills the container (using
docker kill id
), but does not remove the ENV state (stored in kubernetes). K8s should recover the app, including any provided ENV keys.