feat: Adds protected_hours and time_zone_id to mongodbatlas_maintenance_window
#3195
Conversation
|
This PR has gone 7 days without any activity and meets the project’s definition of "stale". This will be auto-closed if there is no new activity over the next 7 days. If the issue is still relevant and active, you can simply comment with a "bump" to keep it open, or add the label "not_stale". Thanks for keeping our repository healthy! |
…y checked at resource)
…aintenance window resources
EspenAlbert
changed the title
protected_hours and time_zone_id to mongodbatlas_maintenance_window
|
APIx bot: a message has been sent to Docs Slack channel |
| @@ -44,4 +44,12 @@ In addition to all arguments above, the following attributes are exported: | |||
| * `start_asap` - Flag indicating whether project maintenance has been directed to start immediately. If you request that maintenance begin immediately, this field returns true from the time the request was made until the time the maintenance event completes. | |||
| * `number_of_deferrals` - Number of times the current maintenance event for this project has been deferred, there can be a maximum of 2 deferrals. | |||
| * `auto_defer_once_enabled` - Flag that indicates whether you want to defer all maintenance windows one week they would be triggered. | |||
| * `protected_hours` - (Optional) Defines the time period during which there will be no standard updates to the clusters. See [Protected Hours](#protected-hours). | |||
There was a problem hiding this comment.
should we document the default protected hours value if not specified? is it 0,0 the default?
There was a problem hiding this comment.
Good question. I asked on the ticket.
My guess is that it will be empty (no protected hours)
There was a problem hiding this comment.
also I don't know if there is a limit, e.g. can you set the 24h as protected? (i guess not because then maintenance can't happen). maybe we can reference some official doc for more info.
There was a problem hiding this comment.
There is a link 20 lines below.
There was a problem hiding this comment.
ah, thanks, and the answer is there: The length of your protected hours window cannot exceed 18 hours.
There was a problem hiding this comment.
Upstream replied that they have an internal default.
Description
Adds protected_hours and time_zone_id to mongodbatlas_maintenance_window
Link to any related issue(s): CLOUDP-291819
Type of change:
Required Checklist:
Further comments