Search: "deployment plan"

. (#1542) Bug fixes Deploy - Deployment plan execution: The failure message shown during release preparation has been improved to be more descriptive. (#1568) Deploy - Releases: We fixed an issue where the UI of the Create phase and Deploy phase were not aligned since the Releases screen did not show the new additions, but you can find them in the Release details popup. (#1675) Manage - Explore - Topic browser: We fixed two problems with the topic browser.

. (#1542) ==== Bug fixes ==== * Deploy - Deployment plan execution: The failure message shown during release preparation has been improved to be more descriptive. (#1568) * Deploy - Releases: We fixed an issue where the UI of the Create phase and Deploy phase were not aligned since the Releases screen did not show the new additions, but you can find them in the Release details popup. (#1675) * Manage - Explore - Topic browser: We fixed two problems with the topic browser. ** When navigating to the last page of messages on a topic’s partition, the amount of messages shown in the paging will now correspond to the number of messages on that partition (#1714) ** The first page of messages on a topic’s partition will now include the last message, with offset 1 below the ‘last offset’. * Manage - Export - Data sink: When opening this page on an empty data sink bucket, there will be a warning on top of the page (“no results found”). (#1096) ==== Remarks ==== * General - Portal: We have removed part of our platform's functionality as it was not used anymore.

. == **Bug Fixes** == //__Deploy - Deployment Plan Execution__// The failure message shown during release preparation has been improved to be more descriptive.

Deploy - Release Execution: The description of a manual step in the deployment plan is only shown once while deploying. (#933) Manage - Alerting - Triggers: Fixed synchronization issue for log triggers, preventing unexpected behavior when all log triggers must be re-sent (#961) Remarks General - Portal: We have removed part of our platform's functionality as it was not used anymore.

. * Deploy - Release Execution: The description of a manual step in the deployment plan is only shown once while deploying. (#933) * Manage - Alerting - Triggers: Fixed synchronization issue for log triggers, preventing unexpected behavior when all log triggers must be re-sent (#961) ==== Remarks ==== * General - Portal: We have removed part of our platform's functionality as it was not used anymore. * General - Help Text: We have updated our help text widget to align it with the new UI options in Mendix. (#1757)

For automated test cases, a warning about broken test cases is shown to users who want to create a new version in the flow designer. //__Deploy - Deployment Plan Execution__// A manual step in the deployment plan is shown only once during deployment.

Key concepts == {{warning}}Regardless of what your change entails you always need to execute the deployment plan to deploy and actualize the changes on your environment.

Once you have created your new release, you can use the deployment plan steps to activate the changes on both flow and property levels. More information on how to do this can be found in this [[microlearning>>doc:Main.eMagiz Academy.Microlearnings.Crash Course.Crash Course Platform.crashcourse-platform-deploy-execute-deployment-plan-gen3.WebHome||target="blank"]]. == 4.

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.

. * 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.

. === 3.3 Actualize changes === To effectuate the changes made to your deployed architecture, you should create a new release and deploy this via the deployment plan. In case you need more information on the creation of releases or deploying release you can check that information [[here>>doc:Main.eMagiz Academy.Microlearnings.Crash Course.Crash Course Platform.crashcourse-platform-deploy-create-new-release||target="blank"]] and [[here>>doc:Main.eMagiz Academy.Microlearnings.Crash Course.Crash Course Platform.crashcourse-platform-deploy-execute-deployment-plan-gen3.WebHome||target="blank"]]. == 4.

Suggested Additional Readings == If you are interested in this topic and want more information, please read the help text provided by eMagiz and check out these links: * [[Crash Courses (Menu)>>doc:Main.eMagiz Academy.Microlearnings.Crash Course.WebHome||target="blank"]] ** [[Crash Course Platform (Navigation)>>doc:Main.eMagiz Academy.Microlearnings.Crash Course.Crash Course Platform.WebHome||target="blank"]] *** [[Creating a new Release (Explanation)>>doc:Main.eMagiz Academy.Microlearnings.Crash Course.Crash Course Platform.crashcourse-platform-deploy-create-new-release||target="blank"]] *** [[Deploy a release (Explanation)>>doc:Main.eMagiz Academy.Microlearnings.Crash Course.Crash Course Platform.crashcourse-platform-deploy-execute-deployment-plan-gen3.WebHome||target="blank"]] * [[Intermediate Level (Menu)>>doc:Main.eMagiz Academy.Microlearnings.Intermediate Level.WebHome||target="blank"]] ** [[eMagiz Cloud Management (Navigation)>>doc:Main.eMagiz Academy.Microlearnings.Intermediate Level.eMagiz Cloud Management.WebHome||target="blank"]] *** [[Apply to Environment (Explanation)>>Main.eMagiz Academy.Microlearnings.Intermediate Level.eMagiz Cloud Management.intermediate-emagiz-cloud-management-apply-to-environment||target="blank"]] * [[Expert Level (Menu)>>doc:Main.eMagiz Academy.Microlearnings.Expert Level.WebHome||target="blank"]] ** [[Solution Architecture (Navigation)>>doc:Main.eMagiz Academy.Microlearnings.Expert Level.Solution Architecture.WebHome||target="blank"]] *** [[How to Determine Needed Memory (Explanation)>>doc:Main.eMagiz Academy.Microlearnings.Expert Level.Solution Architecture.expert-solution-architecture-determining-needed-memory||target="blank"]] * [[Configure needed memory (Search Results)>>url:https://docs.emagiz.com/bin/view/Main/Search?

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.

Define deployment plan & create release

crashcourse-platform-exercise-define-deployment-plan-and-create-release

This exercise will explain how you can define a deployment plan for your environment and create a release based on what we have just finished in the Create phase of eMagiz.

Exercise == In this exercise, please execute the following steps in Deploy to prepare your environment for deployment. * Actualize Deploy Architecture by pressing "Apply to environment" in "Start Editing" mode * Create a default deployment plan * Create a release based on what we have just finished in the Create phase of eMagiz. == 3.

{{video attachment="crashcourse-platform-exercise-define-deployment-plan-and-create-release-update.mp4" reference="Main.Videos.Microlearning.WebHome"/}} )))((({{toc/}}))){{/container}} {{/container}}