WILDCARDs and TLS configuration added

[snuids]

I required the TLS config to connect to AMAZON. I also wanted to use wildcard subscritions in order to listens to multiple topics in a single subscription.

Tested with AWS IOT core.

I learned GO this morning so I could have done some things stupidly. Coming from the C++, GO looks nice.

[CLAassistant]

All committers have signed the CLA.

[mathsman5133]

Hi, this would be fantastic - is there any update?

[mampersat]

+1

[mampersat]

Recommend changing this line , adding the TCPS scheme
Current:
tooltip="Supported schemes: TCP (tcp://), TLS (tls://), or WebSocket (ws://)"
Suggested:
tooltip="Supported schemes: TCP (tcp://), TCPS (tcps://), TLS (tls://), or WebSocket (ws://)"

TCPS is the protocol I needed to use to get this to work with our AWS broker.

[snuids]

Hi guys thanks for your positive comments, but I did not have any news from Grafana since 10 months :-(

[NiklasCi]

Suggested change

	var payload = msg.Payload()
	var data map[string]interface{}
	err := json.Unmarshal([]byte(msg.Payload()), &data)
	data["Topic"] = msg.Topic()
	if err == nil {
	log.DefaultLogger.Info("%s", data)
	payload, _ = json.Marshal(data)
	}
	var data map[string]interface{}
	err := json.Unmarshal([]byte(msg.Payload()), &data)
	if err != nil {
	log.DefaultLogger.Error("Failed to unmarshal payload of", msg)
	return
	}
	data["Topic"] = msg.Topic()
	payload, err := json.Marshal(data)
	if err != nil {
	log.DefaultLogger.Error("Failed to marshal data to new payload", data)
	return
	}