19 docs tagged with "cli"

The Cloud Foundry (CF) CLI (Command Line Interface) integration is also Digital.ai Deploy integration for the CloudFoundry server which makes use of CF CLI.

If you configured your Deploy server to use a self-signed certificate, you will notice that trying to connect with a normal command-line interface (CLI) configuration will fail:

You can install the Deploy command-line interface (CLI) on any remote computer and connect to the Deploy server.

This topic describes how to use the Deploy command-line interface (CLI) to deploy an artifact from a Maven repository such as Artifactory or Nexus. This tutorial uses this sample application. This is a WAR file that you can deploy to middleware such as Apache Tomcat or JBoss AS/WildFly.

Use the discovery feature to automatically create an accurate model of your infrastructure in Deploy. During discovery, Deploy scans your middleware environment and creates configuration items (CIs) in the repository. Discovery is part of the Deploy plugin suite, and the exact discovery functionality available depends on the middleware platforms that are present in your environment.

Deploy can perform multiple deployments at the same time. Each of these deployments is called a task. Users instruct Deploy to start a task, stop a task, or cancel a task. After a task is completed or canceled, it is moved to the task archive. This is where Deploy stores its task history. You can query the task archive for tasks, examine the tasks steps and logs, or export the task archive to an XML file.

The repository object in the Deploy command-line interface (CLI) allows you to export the Deploy repository tree to a ZIP file that can be imported into the same Deploy server or into another Deploy server. The ZIP file contains all configuration item (CI) properties, including artifact files.

You can use the Deploy command-line interface (CLI) to control and manage multiple features, such as discovering middleware topology, setting up environments, importing packages, and performing deployments. The CLI connects to the Deploy server using the standard HTTP/HTTPS protocol, so it can be used remotely without firewall issues.

This topic describes the system requirements, installation, and syntax for the XL Command Line Interface (XL CLI) used to support Digital.ai DevOps as Code and blueprints features.

Sometimes, it is necessary to identify all instances of an artifact that has been deployed. For example, if a particular open source library that your application uses has been found to be vulnerable. This topic describes a method for locating artifacts using the Deploy command-line interface (CLI).

You can manage values separately from your DevOps as Code YAML files so that they can be pulled in when applying XL YAML files. DevOps as Code supports multiple methods to configure and manage values including a dedicated file format using the .xlvals extension, environment variables or by explicitly specifying a value in XL CLI command syntax.

The Deploy command-line interface (CLI) provides objects that you can use to interact with the Deploy server.

When Deploy is installed, no permissions are granted to any user. The only users that have permissions granted are the administrator users, and they have all permissions granted to them. Deploy has one predefined administrator user called admin, with the default password admin. For more information, see roles and permissions.

To start the Deploy server, open a command prompt or terminal, go to the XLDEPLOYSERVER_HOME/bin directory, and execute the appropriate command:

You can follow deployment and release pipeline activities defined in your YAML files as they are executed by Deploy or Release using the output provided in the XL Command Line Interface (CLI).

Error when loading terminal

This is an overview of the types that are available in the Deploy command-line interface (CLI).

When using the Deploy command-line interface (CLI)

This topic describes syntax and examples for the XL Command Line Interface (XL CLI). To display the XL CLI help output, type the following from your command line: