dh
DeployHub's CLI using the dhapi module.
Arguments:
ACTION - one of the following
-
deploy- deploy the application to the environment- Usage:
--dhurl --dhuser --dhpass --appname --appversion (optional) --deployenv
- Usage:
-
approve- approve the application version- Usage:
--dhurl --dhuser --dhpass --appname --appversion (optional)
- Usage:
-
move- move the application version using the supplied task- Usage:
--dhurl --dhuser --dhpass --appname --appversion (optional) --from_domain --task
- Usage:
-
updatecomp- create/replace the component version for the application verion-
Usage:
--dhurl --dhuser --dhpass --compname --compvariant (optional) --compversion (optional) --autocompinc (optional) --appname (optional) --appversion (optional) --autoappinc (optional) --compattr --consumes (optional) --provides (optional)
-
Predefined Key/Values:
- BuildId - Identifier for the CI job
- BuildNumber - Build number for the CI job
- BuildUrl - url for the CI job
- Chart - Helm Chart for the component
- ChartNamespace - Name space for the component to be deployed to
- ChartRepo - Helm Chart Repo Name
- ChartRepoUrl - Helm Chart Repo Url
- ChartVersion - Helm Chart version
- CustomAction - Custom Action to assign to the Component
- DockerBuildDate - Timestamp when the image was created
- DockerRepo - Registry which the image was pushed to
- DockerSha - Digest for the image
- DockerTag - Tag for the image
- GitBranch - Git branch in the git repo
- GitCommit - Git commit that triggered the CI job
- GitRepo - Git repo that triggered the CI job
- GitTag - Git tag in the git repo
- GitUrl - Full url to the git repo
- operator - Operator name
- Readme - Readme location in the Git Repo
- ServiceOwner - Owner of the Service
- ServiceOwnerEmail - Email for the Owner of the Service
- ServiceOwnerPhone - Phone number for the Owner of the Service
-
-
assign- assigns a component version to an application verion- Usage:
--dhurl --dhuser --dhpass --compname --compvariant (optional) --compversion (optional) --appname --appversion (optional)
- Usage:
-
kv- assigns the key/values pairs to the component verion- Usage:
--dhurl --dhuser --dhpass --compname --compvariant (optional) --compversion (optional) --kvconfig
- Usage:
-
envscript- creates a bash file from the component toml file- Usage:
--envvars --envvars_sh
- Usage:
-
export- exports a domain including all objects to stdout- Usage:
--dhurl --dhuser --dhpass --from_dom
- Usage:
-
import- imports the export file into the new domain- Usage:
--dhurl --dhuser --dhpass --from_dom --to_dom
Parameter Descriptions:
--dhurl- DeployHub Url--dhuser- DeployHub User--dhpass- DeployHub Password--appname- Application Name--appversion- Application Version--appautoinc- Application Auto Increment Version--deployenv- Deployment Environment--compname- Component Name--compvariant- Component Variant--compversion- Component Version--compautoinc- Component Auto Increment Version--kvconfig- Directory containing the json and properties file--crdatasource- Change Request Data Source for the Component--changerequest- Change Request for Component, use multiple time for each Change Request Id--deploydata- The json file that contains the application, environment and log details--from_domain- Move from domain--task- Task to use for move--envvars- Env Variables TOML file--envvars_sh- Env Variables Output sh file--docker- docker Kind of the component item--file- file Kind of the component item--compattr- Component Attributes, use multiple time for each attr--envs- Environments to Associate App to, use multiple time for each env--importfile- File to Import--fromdom- From Domain--todom- To Domain--msname- New microservice being added to the cluster--msbranch- New microservice branch being added to the cluster--consumes- json file that lists the endpoints the component consumes. [ {"verb", "get", "path": "/weather"}]--provides- json file that lists the endpoints the component provides. [ {"verb", "get", "path": "/checkout"}]
Example Jenkinsfile Snippet: https://github.com/ortelius/compupdate/blob/main/Jenkinsfile
- Usage:
Metadata
Release files for deployhub 9.3.210
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 |
|---|---|---|---|---|
| deployhub-9.3.210.tar.gz | 45.5 kB | Without provenance | Details for deployhub-9.3.210.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| deployhub-9.3.210-py3-none-any.whl | Python 3 | none | any | Details for deployhub-9.3.210-py3-none-any.whl |
Total release size: 85.6 kB
Release files / deployhub-9.3.210.tar.gz
| Download URL | deployhub-9.3.210.tar.gz |
|---|---|
| Size | 45.5 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
a720641e5fa5a89465993ed8e5eed90107dfd87534a170a1062ee1f168fe7b43
|
|
BLAKE2b-256 checksum How to use checksums |
a1d3efa38f7d88512dd3ee2ea2164732cb3b6ee6f2f6db5ad4070aab1561aab9
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/3.2.0 pkginfo/1.5.0.1 requests/2.25.0 setuptools/65.3.0 requests-toolbelt/0.9.1 tqdm/4.47.0 CPython/3.8.14
|
Release files / deployhub-9.3.210-py3-none-any.whl
| Download URL | deployhub-9.3.210-py3-none-any.whl |
|---|---|
| Size | 40.1 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
9305eea83208035331894c907213dc0bc2ef39aebe8124aa405ca82c955ea6c1
|
|
BLAKE2b-256 checksum How to use checksums |
21f9388809a754e49b2bedfda4ac98c708dfbe9d377b0938c027ad028c83c402
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/3.2.0 pkginfo/1.5.0.1 requests/2.25.0 setuptools/65.3.0 requests-toolbelt/0.9.1 tqdm/4.47.0 CPython/3.8.14
|
Security for deployhub 9.3.210
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.