6.5 Custom Deploy Templates
Create your own deployment templates, specific to your environment
A Custom Deploy Template is a reusable deployment configuration that defines the operating system, certificate format, file destinations, and post-deploy script. Templates are used to standardize deployments across multiple agents, especially for custom software or network appliances not covered by auto-discovery.
Operating System
When creating a custom template, the first choice is which operating system it will work on. Paths and other variables are OS-specific.
Starting Template
Often times it’s useful to start from an existing template. When you’re making a custom one, you must choose an existing template to start from. You can pick a basic “empty” one or you can start with something more complicated (Palo Alto/F5)
Destination Paths
When you create a custom template, you can actually specify the specific file paths you’d like, or you can let us pick a default.
| Mode | Description |
|---|---|
| None | Destination paths are unique to each agent and must be specified during import. |
| Automatic | Paths are automatically created relative to the agent’s config directory. $certPath / $CERT_PATH variables will be populated automatically |
| Specific | Static paths that are identical across all target agents. Overrides any auto-discovery hints. |
Variables
Templates can declare variables for parameters that vary by host (e.g., service names, custom log paths). These variables are substituted into the update script at runtime.
You can specify variables and default values for those variables.
Importing Custom Templates
Custom templates appear in the deployment configuration form under the Yours section. Importing a template applies the pre-defined format, script, variables, and tags to the new configuration.