Python client for DCI Control Server
Project description
python-dciclient
The python-dciclient
project provides both the python bindings and a CLI to the DCI Control Server
Installation
The team behind the project offers repositories for Red Hat/CentOS:
yum -y install https://packages.distributed-ci.io/dci-release.el7.noarch.rpm
Then simply run yum install python2-dciclient
for Python 2 or yum install python3-dciclient
for Python 3.
As mentioned above, the package provides two things:
- The CLI: a
dcictl
command is provided. For more detailsdcictl --help
. - The API: a python module one can use to interact with a control server (
dciclient.v1.api.*
)
Credentials
Admitting one has valid credentials to use the DCI Control Server platform, there are two way to specify those informations while using dcictl:
- A dcirc file:
A file where the necessary credentials are stored. This file needs then to be sourced before using dcictl
. Example:
export DCI_LOGIN=foo
export DCI_PASSWORD=bar
export DCI_CS_URL=https://api.distributed-ci.io
or using the API secret method:
export DCI_CLIENT_ID=<client_type>/<client_id>
export DCI_API_SECRET=<api_secret>
export DCI_CS_URL=https://api.distributed-ci.io
Where client_type
can currently be remoteci
or feeder
Which will allow the user to run the command: dcictl team-list
- At the command line level:
One can pass those informations on the CLI level. Example: dcictl --dci-login jdoe --dci-password jdoe --dci-cs-url 'https://api.distributed-ci.io' team-list
or dcictl --dci-client-id <client_type>/<client_id> --dci-api-secret <api_secret> --dci-cs-url 'https://api.distributed-ci.io' team-list
Where client_type
can currently be remoteci
or feeder
For RemoteCIs or Feeders please use the API Secret to authenticate.
List of available commands
Run dcictl --help
command to see the list of the available commands
Commands:
component-create Create a component.
component-delete Delete a component.
component-file-delete Delete a component file.
component-file-download Retrieve a component file.
component-file-list List files attached to a component.
component-file-show Show a component file.
component-file-upload Attach a file to a component.
component-list List all components.
component-show Show a component.
component-status Show an overview of the last jobs associated...
component-update Update a component.
file-delete Delete a file.
file-list List all files.
file-show Show a file.
job-delete Delete a job.
job-list List all jobs.
job-output Show the job output.
job-recheck Recheck a job.
job-results List all job results.
job-show Show a job.
jobdefinition-annotate Annotate a jobdefinition.
jobdefinition-attach-test Attach a test to a jobdefinition.
jobdefinition-create Create a jobdefinition.
jobdefinition-delete Delete a jobdefinition.
jobdefinition-list List all jobdefinitions.
jobdefinition-list-test List tests attached to a jobdefinition.
jobdefinition-set-active Annotate a jobdefinition.
jobdefinition-show Show a jobdefinition.
jobdefinition-unattach-test Unattach a test to a jobdefinition.
jobdefinition-update Update a jobdefinition.
jobstate-list List all jobstates.
jobstate-show Show a jobstate.
purge Purge soft-deleted resources.
remoteci-create Create a remoteci.
remoteci-delete Delete a remoteci.
remoteci-get-data Retrieve data field from a remoteci.
remoteci-list List all remotecis.
remoteci-reset-api-secret Reset a remoteci api secret.
remoteci-show Show a remoteci.
remoteci-update Update a remoteci.
team-create Create a team.
team-delete Delete a team.
team-list List all teams.
team-show Show a team.
team-update Update a team.
topic-create Create a topic.
topic-delete Delete a topic.
topic-list List all topics.
topic-show Show a topic.
user-create Create a user.
user-delete Delete a user.
user-list List all users.
user-show Show a user.
user-update Update a user.
dci-vault
If you want to store secrets in your YAML configuration files
(settings or inventories), you can use the dci-vault
command to do
so. The various agents will then decrypt the secrets
transparently. For example:
$ source dcirc.sh
$ echo -n 42 | dci-vault encrypt_string --stdin-name answer
Reading plaintext input from stdin. (ctrl-d to end input)
answer: !vault |
$ANSIBLE_VAULT;1.1;AES256
36373332616633313866333234303166616237613332316534393834663934663463353433363464
6363626133323036383939633566383139373636633533390a316363393437653663363538343730
65333862633131353030353137636236663036656264393638353464343138623664323731613331
6466636637393865380a336365633465633037623935633866366562373732356635343361353334
3732
Encryption successful
dci-vault
is a thin layer on top of ansible-vault
so all the
sub-commands of ansible-vault
are available.
dci-rhel-latest-kernel-version
The dci-rhel-latest-kernel-version is a utility command to easily get the latest kernel available for the RHEL product.
$ source dcirc.sh
$ dci-rhel-latest-kernel-version --topic RHEL-not-existing
topic RHEL-not-existing not found
- available topics:
RHEL-9.2
RHEL-9.1
RHEL-8.7
RHEL-8.6
RHEL-8.5
RHEL-9.0
RHEL-8.4
RHEL-8.0
RHEL-8.1
RHEL-7.6
RHEL-7.7
RHEL-8.3
RHEL-8.2
RHEL-7.8
RHEL-7.9
RHEL-7-nightly
RHEL-7-milestone
$ dci-rhel-latest-kernel-version --topic-list
available topics:
RHEL-9.2
RHEL-9.1
RHEL-9.0
RHEL-8.7
RHEL-8.6
RHEL-8.5
RHEL-8.4
RHEL-8.3
RHEL-8.2
RHEL-8.1
RHEL-8.0
RHEL-7.9
$ dci-rhel-latest-kernel-version --topic RHEL-9.2
5.14.0-160.el9
dci-create-component
To create a component, you can use the dci-create-component
utility. For example, to create the ga
component called My product
with version 1.0
on the OCP-4.11
topic, use it like that:
$ source dcirc.sh
$ dci-create-component OCP-4.11 "My Product" 1.0 ga
dci-find-latest-component
dci-find-latest-component
allows to find the latest component for a
product. For example to find the latest GA OCP component on the most
recent topic, you can do it like this:
$ source dcirc.sh
$ dci-find-latest-component --tags build:ga OpenShift ocp
To lookup the latest GA OCP component for a specific topic for example OCP-4.11, you can do it like this:
$ source dcirc.sh
$ dci-find-latest-component --topic OCP-4.11 --tags build:ga OpenShift ocp
dci-diff-jobs
dci-diff-jobs
allows to compare the components of 2 jobs:
$ source dcirc.sh
$ dci-diff-jobs --job_id_1 9e3f3a4f-74c5-4bce-9c45-450b27006bed --job_id_2 b55fb5d6-3f01-44ce-9034-26a53e086137
+-----------------------+--------------------------------------+--------------------------------------+
| component | 9e3f3a4f-74c5-4bce-9c45-450b27006bed | b55fb5d6-3f01-44ce-9034-26a53e086137 |
+-----------------------+--------------------------------------+--------------------------------------+
| ocp | 4.9.50 | 4.8.52 |
| redhat-operator-index | v4.9 | v4.8 |
+-----------------------+--------------------------------------+--------------------------------------+
or their tags:
$ source dcirc.sh
$ dci-diff-jobs --tags --job_id_1 9e3f3a4f-74c5-4bce-9c45-450b27006bed --job_id_2 b55fb5d6-3f01-44ce-9034-26a53e086137
+--------------------------------------+--------------------------------------+
| 9e3f3a4f-74c5-4bce-9c45-450b27006bed | b55fb5d6-3f01-44ce-9034-26a53e086137 |
+--------------------------------------+--------------------------------------+
| pipeline-id:8nodes.8225 | Not found |
| inventory:cluster6 | Not found |
| pipeline:install-4.9 | Not found |
| cluster:cluster6 | Not found |
| Not found | pipeline-id:8nodes.8239 |
| Not found | inventory:cluster4 |
| Not found | pipeline:install-4.8 |
| Not found | cluster:cluster4 |
+--------------------------------------+--------------------------------------+
If the --job_id_1
is not specified, the last job in success status is searched.
If the --job_id_2
is not specified, a job is searched with the same
name, remoteci, topic, configuration and url than the job 1.
dci-create-job
To create a job without running a DCI agent, you can use the dci-create-job
utility. It is useful if you want to associate a CI job that is not a DCI job.
$ source dcirc.sh
$ dci-create-job --topic OCP-4.14 --remoteci my-remoteci --name jenkins-job --comment "my comment" --comp 'OpenShift 4.14.10' --tag my-tag --key-value key=42 --data '{"jenkins_url": "https://jenkins.corp.com/job/name/42"}'
License
Apache 2.0
Author Information
Distributed-CI Team distributed-ci@redhat.com
Project details
Release history Release notifications | RSS feed
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
File details
Details for the file dciclient-3.5.0.post202404241416.tar.gz
.
File metadata
- Download URL: dciclient-3.5.0.post202404241416.tar.gz
- Upload date:
- Size: 35.0 kB
- Tags: Source
- Uploaded using Trusted Publishing? No
- Uploaded via: twine/4.0.1 CPython/3.11.6
File hashes
Algorithm | Hash digest | |
---|---|---|
SHA256 | bf444334a17727e7fda4f7e400ce5eb90b24f495afdc32b5c3df7207c813b18d |
|
MD5 | 43f3491a43f4c89b02e801672592667d |
|
BLAKE2b-256 | 99cf7cb629b753520e2ea7706de5e64ff60b0526a526ecc33fa256c0334c3b59 |
File details
Details for the file dciclient-3.5.0.post202404241416-py3-none-any.whl
.
File metadata
- Download URL: dciclient-3.5.0.post202404241416-py3-none-any.whl
- Upload date:
- Size: 60.5 kB
- Tags: Python 3
- Uploaded using Trusted Publishing? No
- Uploaded via: twine/4.0.1 CPython/3.11.6
File hashes
Algorithm | Hash digest | |
---|---|---|
SHA256 | d2a31ae9870c01e11015dcff935ec1097fdca8f84f0432396787b5235af599a2 |
|
MD5 | a0ad6cc78167a6db6f50fe963e0b1fb8 |
|
BLAKE2b-256 | 33c405d5f13d1fd220f9fc57983560e866e6d1054c48dd5da12d0ca60a429a63 |