datacatalog-custom-model-manager
A Python package intended to load user-specified metadata models into Google Cloud Data Catalog, comprising Custom Entries, Tag Templates, and Tags.
It is powered by datacatalog-custom-entries- manager, datacatalog- tag-template-processor, and datacatalog-tag-manager, leveraging their features in the format of a single CLI.
Load Custom Model
From CSV files
- SCHEMAS
Loading custom models from CSV requires a folder (--files-folder argument in the below commands)
containing three files: entries.csv, tag_templates.csv, and tags.csv. Please refer to the
following external resources for further details on their layouts:
| FILE | LAYOUT DOCUMENTATION |
|---|---|
entries.csv |
datacatalog-custom-entries-manager README |
tag_templates.csv |
datacatalog-tag-template-processor README |
tags.csv |
datacatalog-tag-manager README |
- SAMPLE INPUT
- sample-input/egeria-business-glossary for reference;
- Sample metadata for datacatalog-custom-model-manager (Google Sheets) might help to create/export the mandatory CSV files.
- COMMANDS
Python + virtualenv
pip install datacatalog-custom-model-manager
datacatalog-custom-model load \
--files-folder <CSV-FILES-PATH> \
--project-id <YOUR-PROJECT-ID> --location-id <YOUR-LOCATION-ID> \
[--delete-existing-tag-templates]
Docker
docker build --rm --tag datacatalog-custom-model-manager .
docker run --rm --tty \
--volume <CREDENTIALS-FILE-FOLDER>:/credentials --volume <CSV-FILE-FOLDER>:/data \
datacatalog-custom-model-manager load \
--files-folder <CSV-FILES-PATH> \
--project-id <YOUR-PROJECT-ID> --location-id <YOUR-LOCATION-ID> \
[--delete-existing-tag-templates]
Metadata
Release files for datacatalog-custom-model-manager 0.1.1
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 | Actions |
|---|---|---|---|---|
| datacatalog-custom-model-manager-0.1.1.tar.gz | 3.7 kB | Without provenance | Details for datacatalog-custom-model-manager-0.1.1.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| datacatalog_custom_model_manager-0.1.1-py3-none-any.whl | Python 3 | none | any | Details for datacatalog_custom_model_manager-0.1.1-py3-none-any.whl |
Total release size: 8.8 kB
Release files / datacatalog-custom-model-manager-0.1.1.tar.gz
| Download URL | datacatalog-custom-model-manager-0.1.1.tar.gz |
|---|---|
| Size | 3.7 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
a80a50d7c5114c36ad9644d79680818007c05104df1c3899aa5832cee87a8052
|
|
BLAKE2b-256 checksum How to use checksums |
71ce9cff321d80b676e72221e6fe228a081a62eabd6650b9df3b0f001ff8527d
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/3.3.0 pkginfo/1.6.1 requests/2.25.1 setuptools/40.6.2 requests-toolbelt/0.9.1 tqdm/4.55.0 CPython/3.6.12
|
Release files / datacatalog_custom_model_manager-0.1.1-py3-none-any.whl
| Download URL | datacatalog_custom_model_manager-0.1.1-py3-none-any.whl |
|---|---|
| Size | 5.1 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
b413912e9b00eb0dcc83f96bfea8d451e7eb7054eb21aa095d462b2edad64d9a
|
|
BLAKE2b-256 checksum How to use checksums |
fd3d27c3cfc70590d20387a382708568d77309b782248bc67e95dee25f1c97c0
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/3.3.0 pkginfo/1.6.1 requests/2.25.1 setuptools/40.6.2 requests-toolbelt/0.9.1 tqdm/4.55.0 CPython/3.6.12
|
Security for datacatalog-custom-model-manager 0.1.1
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.