This message was deleted.

Yes, the idea is that it’ll treat WIREMOCK_* env vars as safe by default, but anything else needs to be explicitly approved

Ahh ok that’s kinda what I thought but couldn’t get that to work. Can I just double check; in my example, if I exposed the env var like so:

-e WIREMOCK_BASE_URL='<http://production.google.com|production.google.com>'

Would the response body then expect

"baseURL": "{{systemValue type='ENVIRONMENT' key='BASE_URL'}}"

or

"baseURL": "{{systemValue type='ENVIRONMENT' key='WIREMOCK_BASE_URL'}}"

I can experiment further; just incase you know off the top of your head 🙏

I’m pretty certain you need to use the full key, but that is off the top of my head

Awesome; thanks as always Tom 😎 I was probably doing something daft yesterday