AWS plugin
This topic outlines the AWS plugin for Deploy, which supports launching, managing, and configuring various AWS services.
This topic outlines the AWS plugin for Deploy, which supports launching, managing, and configuring various AWS services.
Transitioning a microservice application to the Amazon Web Services (AWS) cloud infrastructure can be a daunting and complex task for a development team new to AWS. The Deploy/Release Blueprints for AWS can streamline the process of creating the AWS infrastructure, orchestrating the pipeline using Release, and deploying applications using Deploy.
This how-to demonstrates how you can leverage the Digital.ai Deploy and Release applications' capabilities and deploy your application to the Amazon EKS test and prod namespaces.
This how-to demonstrates how you can leverage the Digital.ai Deploy application's DevOps as code capabilities and deploy applications to Amazon Web Services (AWS) using Terraform.
The Azure Resource Manager (ARM) allows users to deploy applications to Azure using declarative JSON templates. In the DevOps as Code CLI, you can use the Basic ARM Template to run blueprints on the platforms hosted on Azure, by creating ARM templates. This can greatly simplify the process of provisioning resources from Deploy and Release in an Azure environment.
Introduction
A blueprint repository is a remote repository that contains templates and source code for blueprint functionality. Each time you run the XL CLI xl blueprint command, it fetches files from the blueprint repository.
This topic illustrates how to use the diagnostic mode in Deploy.
If you plan to use an existing database—one that is not created by default by the Operator-based installer—you must configure the relevant database parameters in the daideploy_cr.yaml file.
If you plan to use an existing database—one that is not created by default by the Operator-based installer—you must configure the relevant database parameters in the daideploy_cr.yaml file.
If you plan to use an existing message queue — one that is not created by default by the Operator-based installer — you must configure the relevant MQ parameters in the daideploy_cr.yaml file.
This topic illustrates how to use an external database instead of the one that is provided with the operator itself.
If you plan to use an external message queue, instead of the RabbitMQ provided with the operator—you must configure the relevant parameters in the external-mq-patch.yaml file.