Storage consul: allow comma in service_tags

[deniszh]

Currently, service_tags parameter of consul storage should contain a comma-separated list of tags, which means that tag can't contain a comma. it would be nice to have some way to insert it.

[fewknow]

This is currently blocking for us to use "OrgName, Inc." when creating a role with pki secrets engine.

resource "vault_pki_secret_backend_role" "role" {
  backend = "pki"
  name    = "my_role"
  ou      = ["OrgName, Inc."]
}

This ends up creating

locality                              []
max_ttl                               0s
no_store                              false
not_before_duration                   30s
organization                          [OrgName Inc.]
ou                                    []

So when I try to generate a cert it get this err:

RESPONSE : 
{"errors":["Organization [] doesn't match regexps: [^QRG, Inc\\.$]"]}

[FelipeEmerim]

Since traefik added an option of discovering consul services though service tags this is a major issue for us, as the middlewares are a comma separated list of names.

[tommyalatalo]

service_tags needs to be a HCL list of strings and not a comma separated string. The value that the parameter takes now makes no sense since the config is written in HCL and would very naturally lend itself to this.

[smaddock]

Similar issue in the forums: https://discuss.hashicorp.com/t/how-to-use-a-comma-in-vault-pki/35324/3