Support !secret in JSON constructed with ArduinoJson syntax

[ArsenicBismuth]

Component name

json

Link to component documentation on our website

https://esphome.io/components/json/

Describe the enhancement

Currently there are two ways of defining JSON as defined in: https://esphome.io/components/http_request/#examples
1st one which only support strings (and can't nest AFAIK?):

on_...:
  - http_request.post:
      url: https://esphome.io
      json:
        key: !lambda |-
          return id(my_sensor).state;
        greeting: "Hello World"

    # Will send:
    # {"key": "42.0", "greeting": "Hello World"}

And using ArduinoJson syntaxt which supports almost everything including nested JSON:

on_...:
  - http_request.post:
      url: https://esphome.io
      json: |-
        root["sensor"] = "gps";
        root["time"] = 1351824120;
        root["nest"][0]["apple"] = "good";

    # Will send:
    # {"sensor":"gps","time":1351824120,"nest":[{"apple":"good"}]}

But the problem is, the 2nd syntax doesn't support using !secrets. Adding it would give me this error:

smart-door.yaml: In lambda function:
smart-door.yaml:140:21: error: 'secret' was not declared in this scope; did you mean 'socket'?

Use cases

Allow sending HTTP request using values stored in secrets.

Anything else?

A workaround that I tried is using globals, but it doesn't really work when putting such as initial_value: !secret API_KEY, got some strange errors. The only way I can make this work is via another text component that sets its initial value as secret and reference that using id() in the json.

[github-actions[bot]]

🏷️ I've automatically added the component: json label to help categorize this feature request.

[ssieb]

I think that isn't possible. Use a substitution to pull in the secret, then use that in your json.

[ArsenicBismuth]

Yeah I know that's not possible now, that's why it's a feature enhancement request.

[ssieb]

I don't think it's possible at all as it would break yaml parsing.

[ArsenicBismuth]

Ahhh gotcha, thanks

[ssieb]

Also, I think you misunderstood the workaround.

substitutions:
  my_value: !secret something

   json:
     root["sensor"] = "$my_value";

[ArsenicBismuth]

Ohhhh so that's how, thanks! Yeah that's def much better than globals. I didn't know of that syntax and just read an unrelated issue post where someone used substitution a few seconds ago.

Will mark solved coz the benefit is non-existent with easier alternative.