Update go client (#743)

Closes #742

docs/resources/dashboard.md

@@ -6,7 +6,7 @@ page_title: " datadog_dashboard"
 
 Provides a Datadog dashboard resource. This can be used to create and manage Datadog dashboards.
 
-~> **Note:** This resource uses the new [Dashboard API](https://docs.datadoghq.com/api/v1/dashboards/) which adds new features like better validation and support for the [Group widget](https://docs.datadoghq.com/graphing/widgets/group/). Additionally, this resource unifies [`datadog_timeboard`](timeboard.html) and [`datadog_screenboard`](screenboard.html) resources to allow you to manage all of your dashboards using a single format.
+~> **Note:** This resource uses the new [Dashboard API](https://docs.datadoghq.com/api/v1/dashboards/) which adds new features like better validation and support for the [Group widget](https://docs.datadoghq.com/dashboards/widgets/group/). Additionally, this resource unifies [`datadog_timeboard`](timeboard.html) and [`datadog_screenboard`](screenboard.html) resources to allow you to manage all of your dashboards using a single format.
 
 ## Example Usage: Create a new Datadog dashboard - Ordered layout
 
@@ -688,7 +688,7 @@ Nested `widget` blocks have the following structure:
         -   `request`: (Required) Nested block describing the request to use when displaying the widget. Multiple request blocks are allowed with the following structure:
             -   `q`: (Required) The metric query to use in the widget.
             -   `style`: (Optional) Style of the widget graph. One nested block is allowed with the following structure:
-                -   `palette`: (Optional) Color palette to apply to the widget. The available options are available here: https://docs.datadoghq.com/graphing/widgets/timeseries/#appearance.
+                -   `palette`: (Optional) Color palette to apply to the widget. The available options are available here: https://docs.datadoghq.com/dashboards/widgets/timeseries/#appearance.
         -   `title`: (Optional) The title of the widget.
         -   `title_size`: (Optional) The size of the widget's title. Default is 16.
         -   `title_align`: (Optional) The alignment of the widget's title. One of "left", "center", or "right".
@@ -719,7 +719,7 @@ Nested `widget` blocks have the following structure:
         -   `request`: (Required) Nested block describing the request to use when displaying the widget. Multiple request blocks are allowed with the following structure:
             -   `q`: (Required) The metric query to use in the widget.
             -   `style`: (Optional) Style of the widget graph. One nested block is allowed with the following structure:
-                -   `palette`: (Optional) Color palette to apply to the widget. The available options are available here: https://docs.datadoghq.com/graphing/widgets/timeseries/#appearance.
+                -   `palette`: (Optional) Color palette to apply to the widget. The available options are available here: https://docs.datadoghq.com/dashboards/widgets/timeseries/#appearance.
         -   `yaxis`: (Optional) Nested block describing the Y-Axis Controls. The structure of this block is described [below](dashboard.html#nested-widget-axis-blocks)
         -   `show_legend`: (Optional) Whether or not to show the legend on this widget.
         -   `legend_size`: (Optional) The size of the legend displayed in the widget.
@@ -743,7 +743,7 @@ Nested `widget` blocks have the following structure:
         -   `group`: (Optional) The list of tags to group nodes by.
         -   `scope`: (Optional) The list of tags to filter nodes by.
         -   `style`: (Optional) Style of the widget graph. One nested block is allowed with the following structure:
-            -   `palette`: (Optional) Color palette to apply to the widget. The available options are available here: https://docs.datadoghq.com/graphing/widgets/timeseries/#appearance.
+            -   `palette`: (Optional) Color palette to apply to the widget. The available options are available here: https://docs.datadoghq.com/dashboards/widgets/timeseries/#appearance.
             -   `palette_flip`: (Optional) Boolean indicating whether to flip the palette tones.
             -   `fill_min`: (Optional) Min value to use to color the map.
             -   `fill_max`: (Optional) Max value to use to color the map.
@@ -864,7 +864,7 @@ Nested `widget` blocks have the following structure:
             -   `display_type`: (Optional) Type of display to use for the request. Available values are: `area`, `bars`, or `line`.
             -   `on_right_yaxis`: (Optional) Boolean indicating whether the request will use the right or left Y-Axis.
             -   `style`: (Optional) Style of the widget graph. One nested block is allowed with the following structure:
-                -   `palette`: (Optional) Color palette to apply to the widget. The available options are available here: https://docs.datadoghq.com/graphing/widgets/timeseries/#appearance.
+                -   `palette`: (Optional) Color palette to apply to the widget. The available options are available here: https://docs.datadoghq.com/dashboards/widgets/timeseries/#appearance.
                 -   `line_type`: (Optional) Type of lines displayed. Available values are: `dashed`, `dotted`, or `solid`.
                 -   `line_width`: (Optional) Width of line displayed. Available values are: `normal`, `thick`, or `thin`.
             -   `metadata`: (Optional). Used to define expression aliases. Multiple nested blocks are allowed with the following structure:
@@ -938,7 +938,7 @@ Nested `conditional_formats` blocks have the following structure:
 
 -   `comparator`: (Required) Comparator to apply from: One of `>`, `>=`, `<`, or `<=`.
 -   `value`: (Required) Value for the comparator.
--   `palette`: (Required) Color palette to apply; One of `blue`, `custom_bg`, `custom_image`, `custom_text`, `gray_on_white`, `green`, `green_on_white`, `grey`, `orange`, `red`, `red_on_white`, `white_on_gray`, `white_on_green`, `white_on_red`, `white_on_yellow`, or `yellow_on_white`.
+-   `palette`: (Required) Color palette to apply; One of `blue`, `custom_bg`, `custom_image`, `custom_text`, `gray_on_white`, `grey`, `green`, `orange`, `red`, `red_on_white`, `white_on_gray`, `white_on_green`, `green_on_white`, `white_on_red`, `white_on_yellow`, `yellow_on_white`, `black_on_light_yellow`, `black_on_light_green` or `black_on_light_red`.
 -   `custom_bg_color`: (Optional) Color palette to apply to the background, same values available as palette.
 -   `custom_fg_color`: (Optional) Color palette to apply to the foreground, same values available as palette.
 -   `image_url`: (Optional) Displays an image as the background.
@@ -961,7 +961,7 @@ Nested `widget` `custom_link` blocks have the following structure:
 
 ### Nested `apm_query`, `log_query`, `network_query` and `rum_query` blocks
 
-Nested `apm_query`, `log_query`, `network_query` and `rum_query` blocks have the following structure (Visit the [ Graph Primer](https://docs.datadoghq.com/graphing/) for more information about these values):
+Nested `apm_query`, `log_query`, `network_query` and `rum_query` blocks have the following structure (Visit the [ Graph Primer](https://docs.datadoghq.com/dashboards/) for more information about these values):
 
 -   `index`: (Required)
 -   `compute`: (Optional). One of `compute` and `multi_compute` is required. The map has the following keys:
@@ -984,7 +984,7 @@ Nested `apm_query`, `log_query`, `network_query` and `rum_query` blocks have the
 
 ### Nested `process_query` blocks
 
-Nested `process_query` blocks have the following structure (Visit the [ Graph Primer](https://docs.datadoghq.com/graphing/) for more information about these values):
+Nested `process_query` blocks have the following structure (Visit the [ Graph Primer](https://docs.datadoghq.com/dashboards/) for more information about these values):
 
 -   `metric`: (Required)
 -   `search_by`: (Required)

go.mod

@@ -1,7 +1,7 @@
 module github.com/terraform-providers/terraform-provider-datadog
 
 require (
-	github.com/DataDog/datadog-api-client-go v1.0.0-beta.10
+	github.com/DataDog/datadog-api-client-go v1.0.0-beta.11
 	github.com/cenkalti/backoff v2.1.1+incompatible // indirect
 	github.com/dnaeon/go-vcr v1.0.1
 	github.com/fatih/color v1.9.0 // indirect

go.sum

@@ -9,8 +9,8 @@ cloud.google.com/go/bigquery v1.0.1/go.mod h1:i/xbL2UlR5RvWAURpBYZTtm/cXjCha9lbf
 cloud.google.com/go/datastore v1.0.0/go.mod h1:LXYbyblFSglQ5pkeyhO+Qmw7ukd3C+pD7TKLgZqpHYE=
 github.com/BurntSushi/toml v0.3.1/go.mod h1:xHWCNGjB5oqiDr8zfno3MHue2Ht5sIBksp03qcyfWMU=
 github.com/BurntSushi/xgb v0.0.0-20160522181843-27f122750802/go.mod h1:IVnqGOEym/WlBOVXweHU+Q+/VP0lqqI8lqeDx9IjBqo=
-github.com/DataDog/datadog-api-client-go v1.0.0-beta.10 h1:3TLeJiTTHw/kLUkwsoYdmb6L6gpKdqJAko8/mOPja8M=
-github.com/DataDog/datadog-api-client-go v1.0.0-beta.10/go.mod h1:/bMeu+q33QzX2JuO5PkGkhU1VYOXIXKEPF6Ck4yR06M=
+github.com/DataDog/datadog-api-client-go v1.0.0-beta.11 h1:4qrBOSR5gAb3XOdQIymgcS6fzanPBBjkrFfVFW23qCo=
+github.com/DataDog/datadog-api-client-go v1.0.0-beta.11/go.mod h1:/bMeu+q33QzX2JuO5PkGkhU1VYOXIXKEPF6Ck4yR06M=
 github.com/DataDog/datadog-go v3.6.0+incompatible h1:ILg7c5Y1KvZFDOaVS0higGmJ5Fal5O1KQrkrT9j6dSM=
 github.com/DataDog/datadog-go v3.6.0+incompatible/go.mod h1:LButxg5PwREeZtORoXG3tL4fMGNddJ+vMq1mwgfaqoQ=
 github.com/agext/levenshtein v1.2.1/go.mod h1:JEDfjyjHDjOF/1e4FlBE/PkbqA9OfWu2ki2W0IB5558=

vendor/modules.txt

@@ -6,7 +6,7 @@ cloud.google.com/go/internal/optional
 cloud.google.com/go/internal/trace
 cloud.google.com/go/internal/version
 cloud.google.com/go/storage
-# github.com/DataDog/datadog-api-client-go v1.0.0-beta.10
+# github.com/DataDog/datadog-api-client-go v1.0.0-beta.11
 github.com/DataDog/datadog-api-client-go
 github.com/DataDog/datadog-api-client-go/api/v1/datadog
 github.com/DataDog/datadog-api-client-go/api/v2/datadog