mqttcloudproviderslib 0.1.8
A library implementing cloud provider authentication for AWS, Azure and Google cloud for use in mqtt messaging and implements a message hub to publish messages in a fan pattern to all providers.
License: MIT
Keywords: mqttcloudproviderslib paho mqtt azure aws gcp messaging

=====================
mqttcloudproviderslib
=====================

A library implementing cloud provider authentication for AWS, Azure and Google cloud for use in mqtt messaging and implements a message hub to publish messages in a fan pattern to all providers.


* Documentation: https://mqttcloudproviderslib.readthedocs.org/en/latest


Development Workflow
====================

The workflow supports the following steps

 * lint
 * test
 * build
 * document
 * upload
 * graph

These actions are supported out of the box by the corresponding scripts under _CI/scripts directory with sane defaults based on best practices.
Sourcing setup_aliases.ps1 for windows powershell or setup_aliases.sh in bash on Mac or Linux will provide with handy aliases for the shell of all those commands prepended with an underscore.

The bootstrap script creates a .venv directory inside the project directory hosting the virtual environment. It uses pipenv for that.
It is called by all other scripts before they do anything. So one could simple start by calling _lint and that would set up everything before it tried to actually lint the project

Once the code is ready to be delivered the _tag script should be called accepting one of three arguments, patch, minor, major following the semantic versioning scheme.
So for the initial delivery one would call

    $ _tag --minor

which would bump the version of the project to 0.1.0 tag it in git and do a push and also ask for the change and automagically update HISTORY.rst with the version and the change provided.


So the full workflow after git is initialized is:

 * repeat as necessary (of course it could be test - code - lint :) )

   * code
   * lint
   * test
 * commit and push
 * develop more through the code-lint-test cycle
 * tag (with the appropriate argument)
 * build
 * upload (if you want to host your package in pypi)
 * document (of course this could be run at any point)


Important Information
=====================

This template is based on pipenv. In order to be compatible with requirements.txt so the actual created package can be used by any part of the existing python ecosystem some hacks were needed.
So when building a package out of this **do not** simple call

    $ python setup.py sdist bdist_egg

**as this will produce an unusable artifact with files missing.**
Instead use the provided build and upload scripts that create all the necessary files in the artifact.



Project Features
================

* TODO




History
-------

0.0.1 (03-02-2020)
---------------------

* First code creation


0.1.0 (04-02-2020)
------------------

* First MVP release.


0.1.1 (04-02-2020)
------------------

* Updated cloud provider schemas with optional entries.


0.1.2 (04-02-2020)
------------------

* Fixed package reference for relative dynamic import.


0.1.3 (04-02-2020)
------------------

* Fixed Azure key contents and subtopic rendering.


0.1.4 (05-02-2020)
------------------

* Fixed bugs with azure provider.


0.1.5 (05-02-2020)
------------------

* Small linting fixes.


0.1.6 (26-04-2021)
------------------

* Bumped dependencies.


0.1.7 (08-06-2021)
------------------

* Bumped dependencies.


0.1.8 (08-06-2021)
------------------

* Bumped dependencies.