Tidying up schema defintion for data, and binary_data attr's

Author: JaylonmcShan03

kubernetes/resource_kubernetes_config_map_v1_data.go

@@ -49,14 +49,16 @@ func resourceKubernetesConfigMapV1Data() *schema.Resource {
 				},
 			},
 			"data": {
-				Type:        schema.TypeMap,
-				Description: "The data we want to add to the ConfigMap.",
-				Required:    true,
+				Type:         schema.TypeMap,
+				Description:  "The data we want to add to the ConfigMap.",
+				AtLeastOneOf: []string{"data", "binary_data"},
+				Optional:     true,
 			},
 			"binary_data": {
 				Type:         schema.TypeMap,
 				Description:  "BinaryData contains the binary data. Each key must consist of alphanumeric characters, '-', '_' or '.'. BinaryData can contain byte sequences that are not in the UTF-8 range. The keys stored in BinaryData must not overlap with the ones in the Data field, this is enforced during validation process. Using this field will require 1.10+ apiserver and kubelet. This field only accepts base64-encoded payloads that will be decoded/encoded before being sent/received to/from the apiserver.",
 				Optional:     true,
+				AtLeastOneOf: []string{"data", "binary_data"},
 				ValidateFunc: validateBase64EncodedMap,
 			},
 			"force": {