No project description provided
Project description
Dynatrace DB Queries Extension Bulk Migrator
Tool to help with creating Extensions 2.0 declarative SQL extensions off of Extensions 1.0 Custom DB Queries extension configurations.
API Authentication
For commands that interact with the Dynatrace API you need to provide an API URL and Access token. These can be provided on the command line but it is recommended to use environment variables:
- DT_URL (e.g. https://xxx.live.dynatrace.com)
- DT_TOKEN
- permissions:
- ReadConfig
- WriteConfig
- extensions.read
- extensions.write
- metrics.read
- permissions:
Commands
Use --help
with any command to view unique options.
Usage: dbqm pull [OPTIONS]
Pull EF1 db queries configurations into a spreadsheet.
╭─ Options ──────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────╮
│ * --dt-url TEXT [env var: DT_URL] [default: None] [required] │
│ * --dt-token TEXT [env var: DT_TOKEN] [default: None] [required] │
│ --output-file TEXT [default: custom.remote.python.dbquery-export.xlsx] │
│ --help Show this message and exit.
dbqm pull
Used to pull all EF1 Custom DB Queries configurations and export them to an Excel sheet for manual review and as an input to later steps.
dbqm build
Used to build extensions from a previously exported configuration excel workbook.
Certificate and key
Before building you need to create a developer key and certificate. These will be used to sign the extension packages. Refer to the steps here for creating the certificate and key file(s). The developer.pem
file will be used in the build command.
Required options
--cert-file-path
path to developer.pem--private-key-path
path to developer.pem--input-file
path to the previously exported configuration exce;--merge-endpoints
tells the tool to merge endpoints based on a matching host or jdbc string (to avoid hitting limits if it were one extension per EF1 DB queries endpoint)--directory
path to where the migrated extensions will be stored locally
Example:
dbqm build --cert-file-path=developer.pem --private-key-path=developer.pem --input-file=custom.remote.python.dbquery-export.xlsx --merge-endpoints --directory=C:\workspaces\migrated_extensions
After running in the directory (default: migrated_extensions) you will see a directory per new extension which will contain a src directory and a signed zip of the new extension.
Project details
Download files
Download the file for your platform. If you're not sure which to choose, learn more about installing packages.
Source Distribution
Built Distribution
Hashes for db_queries_bulk_migrator-0.2.1.tar.gz
Algorithm | Hash digest | |
---|---|---|
SHA256 | ccc239f6eb3792f66228f6b8d48cdaa6ba77941f5f88312275ef5eb2647b2b6e |
|
MD5 | 491f9ec4f2fdd763984e40067e84ed9c |
|
BLAKE2b-256 | 43906b7382e951ecee58ad90115dea5012048cad21d31412aeff7c7a903de5fb |
Hashes for db_queries_bulk_migrator-0.2.1-py3-none-any.whl
Algorithm | Hash digest | |
---|---|---|
SHA256 | df99dd5daaa85d5f2a8cd7cc87702147bf77f34a7c9aacf57f996fd95ebcfa7f |
|
MD5 | af4c88da30cc1f449e5c2e0d8313fe78 |
|
BLAKE2b-256 | 900366f2da729bcf1e1596b0bd0d1e9395ad65a33f329d01cf52d527867ed524 |