Issue

Description

The /info and /agents/{agent_id} endpoints are non function, and should be implemented as per the spec. This will involved upgrading the ws-com-framework to support some extra message varieties.

Tasks/General Thoughts

• Update ws-com-framework to support sending the message data
• Implement /info
• Implement /agents/{agent_id}
• {x] Add tests for both above endpoints
• Refactor the openapi.oas.yml spec as needed to make the endpoints make sense

Issue

Description

As per the OpenAPI spec, in the event an upload files to the api, it should provide a new URL in a UPLOAD_RETRY header so the agent can try the upload again.

Tasks/General Thoughts

• Add UPLOAD_RETRY header
• Add test to ensure it isn't there on successful uploads
• Add test to ensure header appears after 1 failed attempt
• Add test to make sure that after 2 failed try it fails outright without a new header

Now that things are finally coming together, it would be nice to make a Dockerfile.dev file (similar to https://github.com/file-share-platform/front-ui/blob/main/Dockerfile.dev) that uses cargo watch to aid fast end-to-end development.

Description

In the event the central api encounters a failure, we want to forward a more "human" error to our users. To that end, lets setup the human-panic crate.

Tasks/General Thoughts

• Setup the human-panic dependency, to build only for release distributions.
• If possible, write a test for it.