TRIGGERS (for manifest)

The TRIGGERS element defines a set of deployment parameters that can be used when deploying an application with fglgar.

It contains elements which specify programs (.42r or .42m) or scripts to execute when deploying and undeploying applications on the GAS when fglgar is used.
Note: Deployment triggers are typically not required, you can deploy your applications without them.


[<TRIGGERS [component ='comp_name']>]
  1. The comp_name specifies a set of environment context for the runtime required by the DEPLOY and UNDEPLOY programs. If not set, it defaults to the "cpn.gar.execution.local" Web Application component defined in the GAS as.xcf

Child elements

The TRIGGERS element may contain the following child elements:

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

Example MANIFEST with triggers

<TRIGGERS component = 'cpn.gar.execution.local'>
  <DEPLOY>fglrun mydeploy.42r</DEPLOY>
  <UNDEPLOY>fglrun myundeploy.42r</UNDEPLOY>

fglgar with trigger options

In this example, the component value - "cpn.gar.execution.local" - is specified by the --trigger-component at the command line when creating an archive:

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

Note: If the --deploy-trigger fails, the entire deployment will fail. Whereas if the --undeploy-trigger fails, the undeployment is still carried out.

The MANIFEST file is created automatically with the trigger information.

Parent elements

This element is a child of the MANIFEST element in MANIFEST file