Search: "deployment plan"

For more information on this please check out this [[microlearning>>doc:Main.eMagiz Academy.Microlearnings.Crash Course.Crash Course Platform.crashcourse-platform-deploy-execute-deployment-plan-gen3.WebHome||target="blank"]]. ====Bug fixes==== * The content-length header is now removed from all messages.

Furthermore, the components of the API Gateway are the following: ** Gateway infra ** All entry (later replaced with single entries per operation) ** Exit gate (contains a connection to backend provider) These components can be made part of the Release and Deployment plans. The Deploy Architecture will contain the Cloud architecture to be deployed and can be applied with the Design Architecture.

{{/info}} {{info}}In the 3rd generation runtime, you need to create a new release and deploy this with the help of your deployment plan to an environment. After you have deployed the flow, you can test the settings via the Swagger UI, which you can access via the Runtime Dashboard -> View Swagger UI.

Key takeaways == Flow tests are a powerful way in which flows components can be tested without the specific need to deploy them on the eMagiz runtimes using releases and deployment plans. Individual behavior can be tested and verified, without the need to run expensive debug components inside the actual flow.

Setting up a deployment plan

crashcourse-platform-deploy-setup-deployment-plan--default-deployment-plan.png

crashcourse-platform-deploy-setup-deployment-plan-pic1.png

crashcourse-platform-deploy-setup-deployment-plan-gen3

The release is active in that all changes made to it compared to the running environment are applied effectively before executing the deployment. The Deployment plan is defined in the Deployment Plan section under Deploy.

[[image:Main.Images.Microlearning.WebHome@crashcourse-platform-deploy-setup-deployment-plan-pic1.png]] == 3. Defining the Deployment plan == Below is a screenshot of a basic Deployment plan.

[[image:Main.Images.Microlearning.WebHome@crashcourse-platform-deploy-setup-deployment-plan--default-deployment-plan-gen3.png]] Running a deployment plan means machines are stopped, and new images are deployed. eMagiz does this by comparing your currently running release and the recent release you have activated.

Prerequisites == * Basic knowledge of the eMagiz platform * Completed all microlearnings from Deploy till this specific microlearning * Have an environment where you can add releases and that is operational to try out the deployment plan == 2. Key concepts == eMagiz provides the capability to manage your deployments effectively so that all your updated flow components as created in the previous ILM phases of eMagiz.

Select the option set as active to make this the release that the deployment plan will use to deploy the updated, new, and changed flows.

Key takeaways == * The Release defines what is to be deployed on a specific environment, as compared to the Deployment plan that determines what is to be deployed * Use proper naming and clean your old releases regularly.

Prerequisites == * Basic knowledge of the eMagiz platform * Understanding Releases and be able to run a Deployment plan effectively * Understanding Containers and how flows are managed across them == 2.

If you want to know more about when a new image is created for a container, please read this [[microlearning>>doc:Main.eMagiz Academy.Microlearnings.Crash Course.Crash Course Platform.crashcourse-platform-deploy-execute-deployment-plan-gen3.WebHome||target="blank"]]. ** Note that this can be **red** in case the latest changes are not deployed on the certain runtime. For example if your deployment plan stops half way and there were changes which need to be deployed in the second part, you could end up in this situation. * State ** Throughout the lifetime of a container it can have one of the 6 states mentioned below.

crashcourse-platform-manage-alerting-in-emagiz--deployment-plan-help.png

This microlearning will focus on configuring the deployment plan to control various inbound components in a typical group and failover configuration.

Key concepts == This microlearning describes how to configure (parts of) your deployment plan to set up the grouping and, if needed, the failover functionality.

The group name needs to match **exactly** to make it work. * You can control group and failover steps from the deployment plan. * Container inbounds can have a different failover status. == 5.

. * To keep your project manageable, it's recommended to include a manual step in your ACCP or PROD deployment plan to clean up unused resources during every release cycle. == 5.