---
layout: commands
page_title: "Commands: Render"
sidebar_title: "render"
description: "Render the templates within a pack"
---

# Nomad-Pack Render

Command: `nomad-pack render`

Render the templates within a pack

## Usage

Usage: `nomad-pack render <pack-name> [options]`


	Render the specified Nomad Pack and view the results.

Examples:
	# Render an example pack with override variables in a variable file.
	nomad-pack render example --var-file="./overrides.hcl"

	# Render an example pack with cli variable overrides.
	nomad-pack render example --var="redis_image_version=latest" \
		--var="redis_resources={"cpu": "1000", "memory": "512"}"

	# Render an example pack including the outputs template file.
	nomad-pack render example --render-output-template

	# Render an example pack, outputting the rendered templates to file in
	# addition to the terminal. Setting auto-approve allows the command to
	# overwrite existing files.
	nomad-pack render example --to-dir ~/out --auto-approve

    # Render a pack under development from the filesystem - supports current working 
    # directory or relative path
	nomad-pack render . 
	
#### Operation Options

- `-var-file=<string>` - Specifies the path to a variable override file. This can be provided 
				multiple times on a single command to result in a list of files.
- `-var=<key=value>` - Specifies single override variables in the form of HCL syntax and
				can be specified multiple times per command.
- `-name=<string>` - If set, this will be the unique identifier of this deployed
                      instance of the specified pack. If not set, the pack name will
                      be used. This is useful for running more than one instance
			of a pack within the same cluster. Note that this name
                      must be globally unique within a cluster. Running the run
                      command multiple times with the same name, will just re-submit
	                the same pack, and apply changes if you have made any to
                      the underlying pack. Be mindful that, whether you have made
                      changes or not, the underlying Allocations will be replaced. 
                      When managing packs, the name specified here is the name that
                      should be passed to the plan or destroy commands.
                      

#### Approval Options

- `-auto-approve` - Automatically answer confirmation prompts in the affirmative.

#### Render Options

- `-registry=<string>` - Specific registry name containing the pack to be rendered.
If not specified, the default registry will be used.
- `-ref=<string>` - Specific git ref of the pack to be rendered. 
Supports tags, SHA, and latest. If no ref is specified, defaults to latest.

Using ref with a file path is not supported.
- `-render-output-template` - Controls whether or not the output template file within the
                      pack is rendered and displayed.
- `-to-dir=<string>` - Path to write rendered job files to in addition to standard
				output.