Metadata Azure Driver
💧 Metadata Azure Data Driver Implementation nevermined.io
Table of Contents
Quickstart
To login in Azure cloud you need to execute the driver with the next environment variables set:
AZURE_CLIENT_ID
AZURE_CLIENT_SECRET
AZURE_TENANT_ID
AZURE_SUBSCRIPTION_ID
To get information about how to create an App principal for Metadata Azure driver in your Azure account, please refer to Azure documentation. Links:
At the moment there is only a first implementation for the data_plugin, but in the future is going to be an instance for the computing plugin as well.
Testing
Automatic tests are setup via Travis, executing tox.
Our test use pytest framework.
New Version
The bumpversion.sh script helps to bump the project version. You can execute the script using as first argument {major|minor|patch} to bump accordingly the version.
Attribution
This project is based in the Ocean Protocol osmosis-azure-driver. It keeps the same Apache v2 License and adds some improvements. See NOTICE file.
License
Copyright 2020 Keyko GmbH
This product includes software developed at
BigchainDB GmbH and Ocean Protocol (https://www.oceanprotocol.com/)
Licensed under the Apache License, Version 2.0 (the "License");
you may not use this file except in compliance with the License.
You may obtain a copy of the License at
http://www.apache.org/licenses/LICENSE-2.0
Unless required by applicable law or agreed to in writing, software
distributed under the License is distributed on an "AS IS" BASIS,
WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
See the License for the specific language governing permissions and
limitations under the License.
Metadata
Release files for nevermined-metadata-driver-azure 0.1.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | |
|---|---|---|---|---|
| nevermined-metadata-driver-azure-0.1.0.tar.gz | 14.6 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| nevermined_metadata_driver_azure-0.1.0-py2.py3-none-any.whl | Python 2, Python 3 | none | any | Details |
Total release size: 28.8 kB
Release files / nevermined-metadata-driver-azure-0.1.0.tar.gz
| Download URL | nevermined-metadata-driver-azure-0.1.0.tar.gz |
|---|---|
| Size | 14.6 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
10fc85814aa31d289ea0e4b94235ac2bd33c37f079c5591bc71f17a4faf9fcf0
|
|
BLAKE2b-256 checksum How to use checksums |
c66205022241a72f631a7d95536369b3c0d8c6252a9899ed046f16bf14603aa3
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/3.2.0 pkginfo/1.6.1 requests/2.25.0 setuptools/49.2.1 requests-toolbelt/0.9.1 tqdm/4.52.0 CPython/3.9.0
|
Release files / nevermined_metadata_driver_azure-0.1.0-py2.py3-none-any.whl
| Download URL | nevermined_metadata_driver_azure-0.1.0-py2.py3-none-any.whl |
|---|---|
| Size | 14.2 kB |
| Tags | Python 2 Python 3 |
|
SHA-256 checksum How to use checksums |
7b1cab2a769fd260bd8ee6946a2eeb639fc3038baf724a4cd945656f7476b706
|
|
BLAKE2b-256 checksum How to use checksums |
4ba74931c708fd270195370449708303ccb58e79c4b6a93e4fb7c7df7e7bfc0b
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/3.2.0 pkginfo/1.6.1 requests/2.25.0 setuptools/49.2.1 requests-toolbelt/0.9.1 tqdm/4.52.0 CPython/3.9.0
|
Security for nevermined-metadata-driver-azure 0.1.0
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.
To learn more about protecting yourself from malicious actors, visit our package security documentation.