github.com/ticketmaster/terraform@v0.10.0-beta2.0.20170711045249-a12daf5aba4f/website/docs/commands/apply.html.markdown (about)

     1  ---
     2  layout: "docs"
     3  page_title: "Command: apply"
     4  sidebar_current: "docs-commands-apply"
     5  description: |-
     6    The `terraform apply` command is used to apply the changes required to reach the desired state of the configuration, or the pre-determined set of actions generated by a `terraform plan` execution plan.
     7  ---
     8  
     9  # Command: apply
    10  
    11  The `terraform apply` command is used to apply the changes required
    12  to reach the desired state of the configuration, or the pre-determined
    13  set of actions generated by a `terraform plan` execution plan.
    14  
    15  ## Usage
    16  
    17  Usage: `terraform apply [options] [dir-or-plan]`
    18  
    19  By default, `apply` scans the current directory for the configuration
    20  and applies the changes appropriately. However, a path to another configuration
    21  or an execution plan can be provided. Execution plans can be used to only
    22  execute a pre-determined set of actions.
    23  
    24  The `dir` argument can also be a [module source](/docs/modules/index.html).
    25  In this case, `apply` behaves as though `init` were called with that
    26  argument followed by an `apply` in the current directory. This is meant
    27  as a shortcut for getting started.
    28  
    29  The command-line flags are all optional. The list of available flags are:
    30  
    31  * `-backup=path` - Path to the backup file. Defaults to `-state-out` with
    32    the ".backup" extension. Disabled by setting to "-".
    33  
    34  * `-lock=true` - Lock the state file when locking is supported.
    35  
    36  * `-lock-timeout=0s` - Duration to retry a state lock.
    37  
    38  * `-input=true` - Ask for input for variables if not directly set.
    39  
    40  * `-auto-approve=true` - Skip interactive approval of plan before applying. In a
    41    future version of Terraform, this flag's default value will change to false.
    42  
    43  * `-no-color` - Disables output with coloring.
    44  
    45  * `-parallelism=n` - Limit the number of concurrent operation as Terraform
    46    [walks the graph](/docs/internals/graph.html#walking-the-graph).
    47  
    48  * `-refresh=true` - Update the state for each resource prior to planning
    49    and applying. This has no effect if a plan file is given directly to
    50    apply.
    51  
    52  * `-state=path` - Path to the state file. Defaults to "terraform.tfstate".
    53    Ignored when [remote state](/docs/state/remote.html) is used.
    54  
    55  * `-state-out=path` - Path to write updated state file. By default, the
    56    `-state` path will be used. Ignored when
    57    [remote state](/docs/state/remote.html) is used.
    58  
    59  * `-target=resource` - A [Resource
    60    Address](/docs/internals/resource-addressing.html) to target. For more
    61    information, see
    62    [the targeting docs from `terraform plan`](/docs/commands/plan.html#resource-targeting).
    63  
    64  * `-var 'foo=bar'` - Set a variable in the Terraform configuration. This flag
    65    can be set multiple times. Variable values are interpreted as
    66    [HCL](/docs/configuration/syntax.html#HCL), so list and map values can be
    67    specified via this flag.
    68  
    69  * `-var-file=foo` - Set variables in the Terraform configuration from
    70    a [variable file](/docs/configuration/variables.html#variable-files). If
    71    a `terraform.tfvars` or any `.auto.tfvars` files are present in the current
    72    directory, they will be automatically loaded. `terraform.tfvars` is loaded
    73    first and the `.auto.tfvars` files after in alphabetical order. Any files
    74    specified by `-var-file` override any values set automatically from files in
    75    the working directory. This flag can be used multiple times.