Manual changes to aws_ssm_maintenance_window schedule value are not reverted by terraform

[tom-henderson]

Terraform Version

0.9.5

Affected Resource(s)

• aws_ssm_maintenance_window

Terraform Configuration Files

resource "aws_ssm_maintenance_window" "maintenance_window" {
  name     = "maintenance-window"
  schedule = "cron(0 0 * * ? *)"
  duration = 2
  cutoff   = 1
}

Expected Behavior

If the maintenance window's schedule value is modified in the AWS console it should be reverted back to the value in the terraform config file on the next apply.

Actual Behavior

Manual changes to the schedule value in the AWS console are not reverted by terraform.

Steps to Reproduce

Please list the steps required to reproduce the issue, for example:

1. terraform apply
2. Modify the cron value manually in the AWS console
3. terraform plan - no changes are found
4. terraform apply - the cron value is unchanged and does not match the value in the configuration file

References

• Possibly provider/aws: Add support for aws_ssm_maintenance_window #14087

[stack72]

Hi @tom-henderson

I have just pushed a PR for this right now and I can see it behaves as follows:

% terraform plan                                                                                                                           ✹ ✭
[WARN] /Users/stacko/Code/go/bin/terraform-provider-aws overrides an internal plugin for aws-provider.
  If you did not expect to see this message you will need to remove the old plugin.
  See https://www.terraform.io/docs/internals/internal-plugins.html
Refreshing Terraform state in-memory prior to plan...
The refreshed state will be used to calculate this plan, but will not be
persisted to local or remote state storage.

aws_ssm_maintenance_window.maintenance_window: Refreshing state... (ID: mw-077d68ef83d17198f)
The Terraform execution plan has been generated and is shown below.
Resources are shown in alphabetical order for quick scanning. Green resources
will be created (or destroyed and then created if an existing resource
exists), yellow resources are being changed in-place, and red resources
will be destroyed. Cyan entries are data sources to be read.

Note: You didn't specify an "-out" parameter to save this plan, so when
"apply" is called, Terraform can't guarantee this is what will execute.

~ aws_ssm_maintenance_window.maintenance_window
    schedule: "cron(0 0 * * ? 0)" => "cron(0 0 * * ? *)"


Plan: 0 to add, 1 to change, 0 to destroy.

[ghost]

I'm going to lock this issue because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues.

If you have found a problem that seems similar to this, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.