github.com/ns1/terraform@v0.7.10-0.20161109153551-8949419bef40/website/source/docs/commands/plan.html.markdown (about)

     1  ---
     2  layout: "docs"
     3  page_title: "Command: plan"
     4  sidebar_current: "docs-commands-plan"
     5  description: |-
     6    The `terraform plan` command is used to create an execution plan. Terraform performs a refresh, unless explicitly disabled, and then determines what actions are necessary to achieve the desired state specified in the configuration files. The plan can be saved using `-out`, and then provided to `terraform apply` to ensure only the pre-planned actions are executed.
     7  ---
     8  
     9  # Command: plan
    10  
    11  The `terraform plan` command is used to create an execution plan. Terraform
    12  performs a refresh, unless explicitly disabled, and then determines what
    13  actions are necessary to achieve the desired state specified in the
    14  configuration files. The plan can be saved using `-out`, and then provided
    15  to `terraform apply` to ensure only the pre-planned actions are executed.
    16  
    17  ## Usage
    18  
    19  Usage: `terraform plan [options] [dir]`
    20  
    21  By default, `plan` requires no flags and looks in the current directory
    22  for the configuration and state file to refresh.
    23  
    24  The command-line flags are all optional. The list of available flags are:
    25  
    26  * `-destroy` - If set, generates a plan to destroy all the known resources.
    27  
    28  * `-detailed-exitcode` - Return a detailed exit code when the command exits.
    29    When provided, this argument changes the exit codes and their meanings to
    30    provide more granular information about what the resulting plan contains:
    31    * 0 = Succeeded with empty diff (no changes)
    32    * 1 = Error
    33    * 2 = Succeeded with non-empty diff (changes present)
    34  
    35  * `-input=true` - Ask for input for variables if not directly set.
    36  
    37  * `-module-depth=n` - Specifies the depth of modules to show in the output.
    38    This does not affect the plan itself, only the output shown. By default,
    39    this is -1, which will expand all.
    40  
    41  * `-no-color` - Disables output with coloring.
    42  
    43  * `-out=path` - The path to save the generated execution plan. This plan
    44    can then be used with `terraform apply` to be certain that only the
    45    changes shown in this plan are applied. Read the warning on saved
    46    plans below.
    47  
    48  * `-parallelism=n` - Limit the number of concurrent operation as Terraform
    49    [walks the graph](/docs/internals/graph.html#walking-the-graph).
    50  
    51  * `-refresh=true` - Update the state prior to checking for differences.
    52  
    53  * `-state=path` - Path to the state file. Defaults to "terraform.tfstate".
    54    Ignored when [remote state](/docs/state/remote/index.html) is used.
    55  
    56  * `-target=resource` - A [Resource
    57    Address](/docs/internals/resource-addressing.html) to target. Operation will
    58    be limited to this resource and its dependencies. This flag can be used
    59    multiple times.
    60  
    61  * `-var 'foo=bar'` - Set a variable in the Terraform configuration. This flag
    62    can be set multiple times. Variable values are interpreted as
    63    [HCL](/docs/configuration/syntax.html#HCL), so list and map values can be
    64    specified via this flag.
    65  
    66  * `-var-file=foo` - Set variables in the Terraform configuration from
    67     a [variable file](/docs/configuration/variables.html#variable-files). If
    68    "terraform.tfvars" is present, it will be automatically loaded first. Any
    69    files specified by `-var-file` override any values in a "terraform.tfvars".
    70    This flag can be used multiple times.
    71  
    72  ## Security Warning
    73  
    74  Saved plan files (with the `-out` flag) encode the configuration,
    75  state, diff, and _variables_. Variables are often used to store secrets.
    76  Therefore, the plan file can potentially store secrets.
    77  
    78  Terraform itself does not encrypt the plan file. It is highly
    79  recommended to encrypt the plan file if you intend to transfer it
    80  or keep it at rest for an extended period of time.
    81  
    82  Future versions of Terraform will make plan files more
    83  secure.