comma separated config becomes unwieldy with more than few certs

[Paul Gear]

At the moment cert_auth_pairs & cert_kubernetes_names must be comma-separated lists. After more than 2 certificates this makes line wrapping rather messy, e.g.

  cert_auth_pairs: foo.example.com=ooph9iNgei3Fah9eegohb4thoshieRoquee4yupheegiesau3pok4ueng9aafoh3, bar.example.com=wohfeeb7Thuk7PieChia4mai3sheig4ohyu4ohpah3ooTohch4thei4ohvoo9Ve3, baz.example.com=xooxih7esah3xog4eghahyeehuPohdeej3iey9ahF4aizaYaew3eingee3shuaL7
  cert_kubernetes_names: foo.example.com=production/foo-example-com-tls,
bar.example.com=production/bar-example-com-tls, baz.example.com=production/baz-example-com-tls

It would be preferred for readability and easy sorting if these could be yaml lists:

  cert_auth_pairs:
    - bar.example.com=wohfeeb7Thuk7PieChia4mai3sheig4ohyu4ohpah3ooTohch4thei4ohvoo9Ve3
    - baz.example.com=xooxih7esah3xog4eghahyeehuPohdeej3iey9ahF4aizaYaew3eingee3shuaL7
    - foo.example.com=ooph9iNgei3Fah9eegohb4thoshieRoquee4yupheegiesau3pok4ueng9aafoh3
  cert_kubernetes_names:
    - bar.example.com=production/bar-example-com-tls
    - baz.example.com=production/baz-example-com-tls
    - foo.example.com=production/foo-example-com-tls

[Joel Sing (jsing)]

Given the existing deployment and original support for comma separate lists, we'd need to also maintain backwards compatibility, however it should be possible to determine what type of content has been supplied and support both.

[Joel Sing (jsing)]

cert_auth_pairs, cert_additional_names and cert_kubernetes_names all now support YAML lists or CSV. It is also worth noting that CSV works with multiline input:

  www1.example.com=abcdef,
  www2.example.com=123456