Update oncall_schedule.md #1513
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
The Schedule HTTP API docs (https://grafana.com/docs/oncall/latest/oncall-api-reference/schedules/) that the oncall_schedule resource uses specify "web" as a valid type value. However, this isn't an available option for the TF resource due to drift or conflict issues. It would be good to clarify the available values ("ical" and "calendar") since this differs from the Schedule HTTP API docs.
|
|
|
In order to lower resource usage and have a faster runtime, PRs will not run Cloud tests automatically. |
julienduchesne
approved these changes
Apr 26, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
The Schedule HTTP API docs (https://grafana.com/docs/oncall/latest/oncall-api-reference/schedules/) that the oncall_schedule resource uses specify "web" as a valid type value.
However, this isn't an available option for the TF resource due to drift or conflict issues. It would be good to clarify the valid values ("ical" and "calendar") since this differs from the Schedule HTTP API docs.