-
Notifications
You must be signed in to change notification settings - Fork 9.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
resource/aws_ssm_maintenance_window: Add end_date, schedule_timezone, and start_date attributes #7040
Conversation
… and start_date attributes Changes: * resource/aws_ssm_maintenance_window: Add `end_date`, `schedule_timezone`, and `start_date` attributes * resource/aws_ssm_maintenance_window: Refactor to call Read after Create * tests/resource/aws_ssm_maintenance_window: Refactor acceptance testing to test all attributes Output from acceptance testing: ``` --- PASS: TestAccAWSSSMMaintenanceWindow_disappears (8.55s) --- PASS: TestAccAWSSSMMaintenanceWindow_basic (14.14s) --- PASS: TestAccAWSSSMMaintenanceWindow_Enabled (18.78s) --- PASS: TestAccAWSSSMMaintenanceWindow_multipleUpdates (20.36s) --- PASS: TestAccAWSSSMMaintenanceWindow_Cutoff (20.94s) --- PASS: TestAccAWSSSMMaintenanceWindow_Duration (21.10s) --- PASS: TestAccAWSSSMMaintenanceWindow_EndDate (28.64s) --- PASS: TestAccAWSSSMMaintenanceWindow_Schedule (30.68s) --- PASS: TestAccAWSSSMMaintenanceWindow_ScheduleTimezone (31.00s) --- PASS: TestAccAWSSSMMaintenanceWindow_StartDate (32.63s) ```
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM 👍
|
||
"end_date": { | ||
Type: schema.TypeString, | ||
Optional: true, |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
do you want some validation on these checking the date format?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The API parameter says it accepts ISO-8601 extended format, which has some slight differences with RFC3339, that would match our normal date validators. The time.RFC3339
format built into Go's standard library doesn't work with all ISO-8601 formats unfortunately.
It looks like we have ISO-8601 needs in other places where it is inconsistently handled, so I have created a technical debt issue to address all these at once (I would think preferably upstream in the provider SDK), but even a common solution in the provider itself is a good start: #7045
|
||
"start_date": { | ||
Type: schema.TypeString, | ||
Optional: true, |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
do you want some validation on these checking the date format?
This has been released in version 1.55.0 of the AWS provider. Please see the Terraform documentation on provider versioning or reach out if you need any assistance upgrading. |
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 feel this issue should be reopened, we encourage creating a new issue linking back to this one for added context. Thanks! |
Closes #6962
Closes #6980
Changes:
end_date
,schedule_timezone
, andstart_date
attributesOutput from acceptance testing: