From 8c9084e0d8a0b4bf97782c16794580ae5fcb70bb Mon Sep 17 00:00:00 2001 From: Marc Rooding Date: Wed, 22 Mar 2017 13:27:49 +0100 Subject: [PATCH] Kubernetes ConfigMap metadata name did not comply to the regex rules (#12955) --- .../docs/providers/kubernetes/r/config_map.html.markdown | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/website/source/docs/providers/kubernetes/r/config_map.html.markdown b/website/source/docs/providers/kubernetes/r/config_map.html.markdown index a1b4ea962..f8ca26c3f 100644 --- a/website/source/docs/providers/kubernetes/r/config_map.html.markdown +++ b/website/source/docs/providers/kubernetes/r/config_map.html.markdown @@ -16,7 +16,7 @@ Config Map can be used to store fine-grained information like individual propert ``` resource "kubernetes_config_map" "example" { metadata { - name = "my_config" + name = "my-config" } data { api_host = "myhost:443" @@ -56,5 +56,5 @@ The following arguments are supported: Config Map can be imported using its name, e.g. ``` -$ terraform import kubernetes_config_map.example my_config +$ terraform import kubernetes_config_map.example my-config ```