15 docs tagged with "provisioning"

This topic outlines the AWS plugin for Deploy, which supports launching, managing, and configuring various AWS services.

This topic describes how CF CLI integration is used in the Digital.ai Deploy server.

This topic describes the Deploy Cloud Foundry plugin, which supports creating spaces, deploying applications, creating routes, binding services, and using manifest files.

This topic describes how to create a provider in Deploy, which is a set of credentials needed to connect to a cloud technology.

This topic describes the process of creating and configuring a provisioning package in Deploy.

This topic provides a step-by-step example that will help you get started with Deploy provisioning in cloud-based environments.

This topic details the features and requirements of the Deploy Terraform Enterprise plugin.

This topic describes how to use Deploy's provisioning feature to create cloud-based environments in a single action. The provisioning process in Deploy is similar to deploying an application.

Deploy's provisioning feature allows you to provide fully automated, on-demand access to your public, private, or hybrid cloud-based environments.

You can use the Deploy Script plugin to enable Deploy to install and provision scripts on hosts.

This topic provides information on using the Deploy Terraform plugin to apply and destroy Terraform resources.

This topic provides information on how to undeploy an application. To remove an application and its components from an environment, you need to undeploy the application. Similarly, to tear down a cloud-based environment provisioned by Deploy, you need to deprovision it.

In Deploy, an orchestrator combines the steps for individual component changes into an overall deployment or provisioning workflow. Orchestrators are also responsible for deciding which parts of the deployment or provisioning plan are executed sequentially or in parallel. You can combine multiple orchestrators for more complex workflows.

You can use placeholders for configuration item (CI) properties that will be replaced with values during provisioning. Use this to create provisioning packages that are environment-independent and reusable.

This topic provides information on using provisioning outputs in templates.