terraform/website/source/docs/enterprise/runs/scheduling-runs.html.md

41 lines
1.6 KiB
Markdown
Raw Normal View History

2017-03-16 20:42:33 +01:00
---
2017-04-03 19:53:38 +02:00
layout: "enterprise"
2017-04-07 06:00:51 +02:00
page_title: "Scheduling - Runs - Terraform Enterprise"
2017-03-17 20:24:20 +01:00
sidebar_current: "docs-enterprise-runs-schedule"
description: |-
Schedule periodic plan runs in Terraform.
2017-03-16 20:42:33 +01:00
---
2017-03-17 20:24:20 +01:00
# Schedule Periodic Plan Runs
2017-03-16 20:42:33 +01:00
2017-04-07 06:00:51 +02:00
-> This is an unreleased beta feature. Please
<a href="mailto:support@hashicorp.com">contact support</a> if you are interested
in helping us test this feature.
2017-03-16 20:42:33 +01:00
2017-04-07 06:00:51 +02:00
Terraform can automatically run a plan against your infrastructure on a
specified schedule. This option is disabled by default and can be enabled by an
2017-03-17 20:24:20 +01:00
organization owner on a per-environment basis.
2017-03-16 20:42:33 +01:00
2017-04-07 06:00:51 +02:00
On the specified interval, a plan can be run that for you, determining any
changes and sending the appropriate notifications.
2017-03-16 20:42:33 +01:00
2017-03-17 20:24:20 +01:00
When used with [automatic applies](/docs/enterprise/runs/automatic-applies.html), this feature can help converge
2017-03-16 20:42:33 +01:00
changes to infrastructure without human input.
2017-04-07 06:00:51 +02:00
Runs will not be queued while another plan or apply is in progress, or if the
environment has been manually locked. Se
[Environment Locking](/docs/enterprise/runs#environment-locking) for more
information.
2017-03-16 20:42:33 +01:00
## Enabling Periodic Plans
2017-04-07 06:00:51 +02:00
To enable periodic plans for an environment, visit the environment settings page
and select the desired interval and click the save button to persist the
changes. An initial plan may immediately run, depending on the state of your
environment, and then will automatically plan at the specified interval.
2017-03-16 20:42:33 +01:00
2017-04-07 06:00:51 +02:00
If you have manually run a plan separately, a new plan will not be queued until
the allotted time after the manual plan ran. This means that the platform simply
ensures that a plan has been executed at the specified schedule.