github.com/hashicorp/packer@v1.14.3/website/content/partials/provisioners/shell-config.mdx (about)

     1  The reference of available configuration options is listed below. The only
     2  required element is either "inline" or "script". Every other option is
     3  optional.
     4  
     5  Exactly _one_ of the following is required:
     6  
     7  - `inline` (array of strings) - This is an array of commands to execute. The
     8    commands are concatenated by newlines and turned into a single file, so
     9    they are all executed within the same context. This allows you to change
    10    directories in one command and use something in the directory in the next
    11    and so on. Inline scripts are the easiest way to pull off simple tasks
    12    within the machine.
    13  
    14  - `script` (string) - The path to a script to upload and execute in the
    15    machine. This path can be absolute or relative. If it is relative, it is
    16    relative to the working directory when Packer is executed.
    17  
    18  - `scripts` (array of strings) - An array of scripts to execute. The scripts
    19    will be uploaded and executed in the order specified. Each script is
    20    executed in isolation, so state such as variables from one script won't
    21    carry on to the next.
    22  
    23  Optional parameters:
    24  
    25  - `binary` (boolean) - If true, specifies that the script(s) are binary
    26    files, and Packer should therefore not convert Windows line endings to Unix
    27    line endings (if there are any). By default this is false.
    28  
    29  - `valid_exit_codes` (list of ints) - Valid exit codes for the script. By
    30    default this is just 0.