Release gate actions

Codar allows you to configure release gate actions at each lifecycle stage. These actions act as a gate between two lifecycle stages. A package has to pass through each action that is defined; hence they are called release gate actions. During promotion of the package, the gate actions defined in each are executed. After all the actions complete successfully, the package transitions to the next lifecycle stage.

You can configure the following release gate actions:

• Deploy - this action deploys the Codar application design on the specified target environment. If the design is a partial design, the micro service designs that meet the requirements of the application design must also be selected.
• Custom - this action executes the specified flow in Operations Orchestration. Typically this action can be used to execute specific tests, with or without a deployment instance.
• Approval - this action is used to configure approvers who will approve the package promotion. It is also used to configure the minimum number of approvals, automatic approvals, and the number of days after which the automatic approval process is triggered.
• Test Set - this action can be used for executing specific tests with or without a deployment instance.
• Script - this action can be used to execute a script on a remote machine, with or without a deployment instance.
  

Deploy action versus Custom action

Deploy actions are typically created to test your environment and to perform a test deployment before promoting your design to the production stage.

Custom actions are typically used to execute operations or tests on a deployed instance. You can also execute custom actions without an instance of a deployment.