39 lines
1.6 KiB
Markdown
39 lines
1.6 KiB
Markdown
|
---
|
||
|
|
title: "Schedule Periodic Plans in Atlas"
|
||
|
|
---
|
||
|
|
|
||
|
|
# Schedule Periodic Plans in Atlas
|
||
|
|
|
||
|
|
<div class="alert-infos">
|
||
|
|
<div class="alert-info">
|
||
|
|
This is an unreleased beta feature. Please <a href="/help/support">contact support</a> if you are interested in helping us test this feature.
|
||
|
|
</div>
|
||
|
|
</div>
|
||
|
|
|
||
|
|
Atlas can automatically run a Terraform plan against
|
||
|
|
your infrastructure on a specified schedule. This option is disabled by default and can be enabled by an
|
||
|
|
organization owner on a per-[environment](/help/glossary#environment) basis.
|
||
|
|
|
||
|
|
On the specified interval, Atlas will automatically queue a plan that
|
||
|
|
runs Terraform for you, determining any changes and sending the appropriate
|
||
|
|
notifications.
|
||
|
|
|
||
|
|
When used with [automatic applies](/help/terraform/runs/automatic-applies), this feature can help converge
|
||
|
|
changes to infrastructure without human input.
|
||
|
|
|
||
|
|
Atlas will not queue new runs while another plan or apply is in progress, or if
|
||
|
|
the environment has been manually locked. See [Environment
|
||
|
|
Locking](/help/terraform/runs#environment-locking) for more information.
|
||
|
|
|
||
|
|
## Enabling Periodic Plans
|
||
|
|
|
||
|
|
To enable periodic plans for an environment, visit the environment settings page in
|
||
|
|
Atlas 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.
|
||
|
|
|
||
|
|
If you have manually run a plan separately, Atlas will not queue a new
|
||
|
|
plan until the alloted time after the manual plan ran. This means that
|
||
|
|
Atlas simply ensures that a plan has been executed at the specified schedule.
|