Skip to main content

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.

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.

Metadata

Release files for mqttcloudproviderslib 0.1.8

For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.

Source distribution (sdist)

Source distribution for mqttcloudproviderslib 0.1.8
File Size Uploaded Provenance
mqttcloudproviderslib-0.1.8.tar.gz 56.3 kB Without provenance Details

Built distribution (wheel)

Table of built distributions (wheels) for mqttcloudproviderslib 0.1.8
File Interpreter ABI Platform
mqttcloudproviderslib-0.1.8-py3.7.egg Legacy Egg format - - Details

Total release size: 90.4 kB

Release files / mqttcloudproviderslib-0.1.8.tar.gz

Download URL mqttcloudproviderslib-0.1.8.tar.gz
Size 56.3 kB
Tags Source
SHA-256 checksum
How to use checksums
f2c3ada306db0174d0d42879195c6347301730d808ed33a6b46ecfd933624078
BLAKE2b-256 checksum
How to use checksums
6f8b001efeb226ad931e31c658b7e360b4757c1e1eaa4052028095b0033387cf
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
No
Uploaded via twine/1.13.0 pkginfo/1.7.0 requests/2.25.1 setuptools/57.0.0 requests-toolbelt/0.9.1 tqdm/4.61.0 CPython/3.7.10

Release files / mqttcloudproviderslib-0.1.8-py3.7.egg

Download URL mqttcloudproviderslib-0.1.8-py3.7.egg
Size 34.2 kB
Tags Egg
SHA-256 checksum
How to use checksums
2e6c61ce320203d45008edc3da3d76ca7e897bbcde88cc9132277a81d69d6e20
BLAKE2b-256 checksum
How to use checksums
3f15a004228e06138e3ec5fdfb9f203b5b18ce6e2700691134b48c31c0d0fca5
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
No
Uploaded via twine/1.13.0 pkginfo/1.7.0 requests/2.25.1 setuptools/57.0.0 requests-toolbelt/0.9.1 tqdm/4.61.0 CPython/3.7.10

Security for mqttcloudproviderslib 0.1.8

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

No provenance found

None of the files in this release were uploaded with provenance metadata.

A note on package security

PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.

Anthropic, PBC Visionary sponsor Bloomberg Visionary sponsor Hudson River Trading Visionary sponsor Meta Visionary sponsor NVIDIA Visionary sponsor Microsoft Sustainability sponsor Depot Continuous Integration AWS Cloud computing and Security Sponsor Datadog Monitoring Fastly CDN Google Download Analytics Sentry Error logging StatusPage Status page