Parent topic: The MANIFEST file
Deploying with Genero Archive / The MANIFEST file

TRIGGERS (for manifest)

The TRIGGERS element defines a set of deployment parameters that can be used when deploying an application with the deployment framework. It takes a component attribute, which specifies the environment context for the runtime (fglrun) required by the DEPLOY and UNDEPLOY elements. These child elements specify commands to execute when deploying and undeploying applications on the GAS.

Syntax

<TRIGGERS component ='comp_name'>
   <DEPLOY> myDeploy </DEPLOY >  
   <UNDEPLOY> myUnDeploy  </UNDEPLOY>  
</TRIGGERS>

Child elements

The TRIGGERS element may contain the following child elements:

  1. Zero or one DEPLOY element.
  2. Zero or one UNDEPLOY element.

Example

<TRIGGERS component = 'cpn.wa.execution.local'>
  <DEPLOY>fglrun mydeploy.42r</DEPLOY>
  <UNDEPLOY>fglrun myundeploy.42r</UNDEPLOY>
</TRIGGERS>
In this example, the component value - cpn.wa.execution.local - can be referenced by the --trigger-component and the DEPLOY value by --deploy-trigger when you are creating an application archive using fglgar, for example:

fglgar --gar --application myapp.xcf --trigger-component  cpn.wa.execution.local --deploy-trigger "fglrun mydeploy.42r" --undeploy-trigger "fglrun myundeploy.42r"

Note:
  • In the case that the --deploy-trigger fails, the entire deployment will fail. Whereas if the --undeploy-trigger fails, the undeployment is still carried out.
  • Deployment triggers are typically not required, you can deploy your applications without them by simply specifying the application's xcf file. See The MANIFEST file.

Parent elements

This element is a child of the MANIFEST element in The MANIFEST file
Parent topic: The MANIFEST file