Used to identify the Service and Module in generated host names. Only letters and numbers allowed.
Select the environments this module will be deployed to.
The URL used to get a hosts availability. For example: {{config.availabilityUrl}}
The URL used to get a hosts version. For example: {{config.versionUrl}}
The user account that the service will run as.
The user account that the service will run as. The Start and Stop command will be invoked as this user.
The folder where you plan to deploy the service. This is documentation only, the system does not use this information or create this folder.
The Start and Stop command will be invoked from this folder. Artifacts and Module files will be copied to this folder. This folder (and sub-folders) are removed during a deployment, and maybe removed during a restart.
The folder where the service will persist data, if required. The data folder should not be a sub folder of the deployment folder.
Only files in this folder are guaranteed to remain across deployments and restarts. The data folder should not be a sub folder of the deployment folder.
Log files should be written to this folder so that they can be automatically collected. Log files must conform to the Log file specification for automatic collection. The logs folder should not be a sub folder of the deployment folder.
Log files are automatically collected on this schedule.
Optional.
Does the service's artifact have a suffix, such as '-jar-with-dependencies'.
The command to start the service or involve a script that will start the service. The command is executed direct on the target host, as the 'Run As User', from the 'Deployment Folder'. If the command contains the pattern {version} then if will be replaced with the selected version.
The command to stop the service or involve a script that will stop the service. The command is executed direct on the target host, as the 'Run As User', from the 'Deployment Folder'.