Enable schedule_layer's end to be null in the JSON encoding #76
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
What
Why
end: null
means the layer doesn't end in the endpointschedules/{id}
.from https://developer.pagerduty.com/api-reference/b3A6Mjc0ODE4NQ-update-a-schedule
pagerduty_schedule.layer.end
PagerDuty/terraform-provider-pagerduty#451 is a related issue. The PagerDuty terraform provider doesn't sendend: null
even whenpagerduty_schedule.layer.end
was deleted.