Clarify the OnCall docs regarding teams (#639)

* Clarify the OnCall docs regarding teams
Closes #637
`team_id` can be confusing. For OnCall, it refers to an OnCall team, not a Grafana team

* Even clearer

Author: julienduchesne

docs/resources/oncall_escalation_chain.md

@@ -28,7 +28,7 @@ resource "grafana_oncall_escalation_chain" "default" {
 
 ### Optional
 
-- `team_id` (String) The ID of the team.
+- `team_id` (String) The ID of the OnCall team. To get one, create a team in Grafana, and navigate to the OnCall plugin (to sync the team with OnCall). You can then get the ID using the `grafana_oncall_team` datasource.
 
 ### Read-Only
 

docs/resources/oncall_integration.md

@@ -34,7 +34,7 @@ resource "grafana_oncall_integration" "test-acc-integration" {
 
 ### Optional
 
-- `team_id` (String) The id of the team.
+- `team_id` (String) The ID of the OnCall team. To get one, create a team in Grafana, and navigate to the OnCall plugin (to sync the team with OnCall). You can then get the ID using the `grafana_oncall_team` datasource.
 - `templates` (Block List, Max: 1) Jinja2 templates for Alert payload. (see [below for nested schema](#nestedblock--templates))
 
 ### Read-Only

docs/resources/oncall_on_call_shift.md

@@ -107,7 +107,7 @@ output "emea_weekday__rolling_users" {
 - `level` (Number) The priority level. The higher the value, the higher the priority.
 - `rolling_users` (List of Set of String) The list of lists with on-call users (for rolling_users event type)
 - `start_rotation_from_user_index` (Number) The index of the list of users in rolling_users, from which on-call rotation starts.
-- `team_id` (String) The ID of the team.
+- `team_id` (String) The ID of the OnCall team. To get one, create a team in Grafana, and navigate to the OnCall plugin (to sync the team with OnCall). You can then get the ID using the `grafana_oncall_team` datasource.
 - `time_zone` (String) The shift's timezone.  Overrides schedule's timezone.
 - `users` (Set of String) The list of on-call users (for single_event and recurrent_event event type).
 - `week_start` (String) Start day of the week in iCal format. Can be MO, TU, WE, TH, FR, SA, SU

docs/resources/oncall_outgoing_webhook.md

@@ -34,7 +34,7 @@ resource "grafana_oncall_outgoing_webhook" "test-acc-outgoing_webhook" {
 - `data` (String) The data of the webhook.
 - `forward_whole_payload` (Boolean) Forwards whole payload of the alert to the webhook's url as POST data.
 - `password` (String) The auth data of the webhook. Used for Basic authentication
-- `team_id` (String) The ID of the team.
+- `team_id` (String) The ID of the OnCall team. To get one, create a team in Grafana, and navigate to the OnCall plugin (to sync the team with OnCall). You can then get the ID using the `grafana_oncall_team` datasource.
 - `user` (String) The auth data of the webhook. Used for Basic authentication.
 
 ### Read-Only

docs/resources/oncall_schedule.md

@@ -58,7 +58,7 @@ resource "grafana_oncall_schedule" "example_schedule" {
 - `ical_url_primary` (String) The URL of the external calendar iCal file.
 - `shifts` (Set of String) The list of ID's of on-call shifts.
 - `slack` (Block List, Max: 1) The Slack-specific settings for a schedule. (see [below for nested schema](#nestedblock--slack))
-- `team_id` (String) The ID of the team.
+- `team_id` (String) The ID of the OnCall team. To get one, create a team in Grafana, and navigate to the OnCall plugin (to sync the team with OnCall). You can then get the ID using the `grafana_oncall_team` datasource.
 - `time_zone` (String) The schedule's time zone.
 
 ### Read-Only

grafana/resource_oncall_escalation_chain.go

@@ -32,7 +32,7 @@ func ResourceOnCallEscalationChain() *schema.Resource {
 			"team_id": {
 				Type:        schema.TypeString,
 				Optional:    true,
-				Description: "The ID of the team.",
+				Description: "The ID of the OnCall team. To get one, create a team in Grafana, and navigate to the OnCall plugin (to sync the team with OnCall). You can then get the ID using the `grafana_oncall_team` datasource.",
 			},
 		},
 	}

grafana/resource_oncall_integration.go

@@ -68,7 +68,7 @@ func ResourceOnCallIntegration() *schema.Resource {
 			"team_id": {
 				Type:        schema.TypeString,
 				Optional:    true,
-				Description: "The id of the team.",
+				Description: "The ID of the OnCall team. To get one, create a team in Grafana, and navigate to the OnCall plugin (to sync the team with OnCall). You can then get the ID using the `grafana_oncall_team` datasource.",
 			},
 			"type": {
 				Type:         schema.TypeString,

grafana/resource_oncall_on_call_shift.go

@@ -64,7 +64,7 @@ func ResourceOnCallOnCallShift() *schema.Resource {
 			"team_id": {
 				Type:        schema.TypeString,
 				Optional:    true,
-				Description: "The ID of the team.",
+				Description: "The ID of the OnCall team. To get one, create a team in Grafana, and navigate to the OnCall plugin (to sync the team with OnCall). You can then get the ID using the `grafana_oncall_team` datasource.",
 			},
 			"name": {
 				Type:         schema.TypeString,

grafana/resource_oncall_outgoing_webhook.go

@@ -32,7 +32,7 @@ func ResourceOnCallOutgoingWebhook() *schema.Resource {
 			"team_id": {
 				Type:        schema.TypeString,
 				Optional:    true,
-				Description: "The ID of the team.",
+				Description: "The ID of the OnCall team. To get one, create a team in Grafana, and navigate to the OnCall plugin (to sync the team with OnCall). You can then get the ID using the `grafana_oncall_team` datasource.",
 			},
 			"url": {
 				Type:        schema.TypeString,

grafana/resource_oncall_schedule.go

@@ -39,7 +39,7 @@ func ResourceOnCallSchedule() *schema.Resource {
 			"team_id": {
 				Type:        schema.TypeString,
 				Optional:    true,
-				Description: "The ID of the team.",
+				Description: "The ID of the OnCall team. To get one, create a team in Grafana, and navigate to the OnCall plugin (to sync the team with OnCall). You can then get the ID using the `grafana_oncall_team` datasource.",
 			},
 			"type": {
 				Type:         schema.TypeString,