Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

[Feedback Requested] Moto 1.0 Plan

See original GitHub issue

I’ve been doing some work on a major upgrade of Moto and would appreciate any feedback/testing.

Big changes:

Deprecate HTTPretty and boto support. These will still exist for now, just with separate decorators (@mock_ec2_deprecated). Since HTTPretty mocks at the socket level, it has caused issues in the past. Since we will primarily be supporting boto3 (and server mode) in the future and boto3 uses requests, we are switching to Responses
More focus more on standalone server mode. I want Moto to work with any programming language. I’ve gone through and ensured that all of the tests work in server-mode and configured that to run on Travis going forward. As the projects moves forward, I see server mode becoming the primary way to use Moto and providing a few helpers for various programming languages.
Drop python 2.6
Moto APIs
- In the past, I’ve been hesitant to start adding custom APIs to manipulate state. I’m coming around on it 😃
- Reset API: I’ve added a reset API to flush all of the current data requests.post("http://motoapi.amazonaws.com/moto-api/reset").
- Exceptions: I’m looking to add a similar endpoint to force Moto to raise exceptions. Maybe requests.post("http://motoapi.amazonaws.com/moto-api/set-next-error", data={"status_code": 400, "body": "Throttling Error: too many requests"}). The subsequent request would then return a 400 response with the designated response body. I would like a better way than this, but can’t think of anything.
Dashboard: A very basic dashboard to be able to see the current state of the system would be nice (list instances, queues, etc).

Feedback welcome.

The deprecation of HTTPretty and cleanup of the server mode is already available on a branch. If anyone is able to give that branch a test and report any issues, it would be very much appreciated.