Centralized config management requires escaping certain characters?

*Original comment by @peterskim12:*

It looks like certain characters might have to be escaped when using the GUI centralized config management editor? Or config management in general?

I've attached a sample config I tried to create in the GUI. The ES password contains some non-alphanumeric characters. I was able to run Logstash with this config file without a problem when disabling config management and running it with bin/logstash -f .

However, when I tried to define this config in the GUI, I kept getting ES 401 responses.

[2017-09-13T15:47:19,569][INFO ][logstash.outputs.elasticsearch] Running health check to see if an Elasticsearch connection is working {:healthcheck_url=>http://localhost:9200/, :path=>"/"}
[2017-09-13T15:47:19,572][WARN ][logstash.outputs.elasticsearch] Attempted to resurrect connection to dead ES instance, but got an error. {:url=>"http://localhost:9200/", :error_type=>LogStash::Outputs::ElasticSearch::HttpClient::Pool::BadResponseCodeError, :error=>"Got response code '401' contacting Elasticsearch at URL 'http://localhost:9200/'"}

I changed the password to one that has only alphanumeric characters and it started working.

LINK REDACTED

Do some characters need escaping when entered through the GUI? Or is this some other problem?