Version 3.0 i coming!

[mgmonteleone]

Thanks to the amazing @dmalik-mdb, we have embarked on a refactor of the Network module to:

• Make it simpler to build modules on top of it.
• Seamlessly handle iterating results.
• Use generators for perf optimization.

As part of this initiative, we have decided on the following:

1. [Very breaking!] Always return objects: The iterable option will be removed, and all endpoints will always return Atlas specific classes. Previously we had a hodgepodge of result types, sometimes returning classes, sometimes returning the raw response. We felt that we should lean in to the "opinionated" nature of this project, and that always returning well documented classes would further ease of using the library.
2. Ensure further test coverage, including testing the correctness of the returned classes.
3. Redo the README, and do a pass of ensuring pydocs are useful.
4. Automate the package release process.

Additionally MongoDB Atlas has rolled out some endpoints with a version 1.5 API version. We intend to abstract away that detail with the impacted endpoints. Until 3.0, @macintacos has provided a workaround using and ENV variable in PR #118, which was released in version 2.0.2. Thanks again to @macintacos for pointing this out!

If anyone else has ideas for priorities for 3.0, please let us know? Higher priority missing endpoints? Bugs? Maybe we should set up a poll for prioritizing current issues? Actually, still not sure if anyone cares, 😄 so please let me know...

MGM

[mgmonteleone]

Yes, its a long delay, but 3.0 is progressing, just released 3.0.1b3.

Includes serverless endpoints as well as some cleanup and a breaking change to more logically name the api key and secret (no longer user and pass)