You can use
cxcli by installing a pre-compiled binary (in several ways), using Docker, or compiling it from source. In the below sections, you can find the steps for each approach.
Install a pre-compiled binary¶
- Add the Homebrew tap:
- Install the Dialogflow CX CLI:
The package in nixpkgs might be slightly outdated, as it is not updated automatically. Use our NUR to always get the latest updates.
Once you do that, you can install the packages.
deb, rpm and apk packages¶
.apk packages from the OSS releases page and install them with the appropriate tools.
You can also set the
VERSION variable to specify
a version instead of using latest.
You can also pass flags and args to cxcli:
This script does not install anything, it just downloads, verifies and runs cxcli. Its purpose is to be used within scripts and CIs.
Download the pre-compiled binaries from the releases page and copy them to the desired location.
Verifying the artifacts¶
All artifacts are checksummed, and the checksum file is signed with cosign.
- Download the files you want along with the
checksums.txt.sigfiles from the releases page:
- Verify the signature:
- If the signature is valid, you can then verify the SHA256 sums match with the downloaded binary:
Our Docker images are signed with cosign.
Verify the signatures:
.sig files are the image
Running with Docker¶
You can also use
cxcli within a Docker container.
To do that, you'll need to execute something more-or-less like the examples below.
Note that the image will almost always have the last stable Go version.
If you need other packages and dependencies, you are encouraged to keep your own image. You can always use cxcli's own Dockerfile as a starting point and iterate on that.
Compiling from source¶
Here you have two options:
If you want to contribute to the project, please follow the steps on our contributing guide.
If you just want to build from source for whatever reason, follow these steps:
get the dependencies:
verify that it works: