Can I use environment variables in an Elastic Synthetics lightweight journey deployed from the command line? This is possible with heartbeat by referencing the variable as ${VAR_NAME}, but with Elastic Synthetics it appears that this looks for a parameter by that name, even if that parameter doesn't exist.
Apologies - I wasn't clear. I'm understand how to use environment variables with parameters, which then pushes local environment variables with the monitor, IIRC. I'm trying to use environment variables defined in the Elastic Agent pod in lightweight monitors. This allows me to manage any synthetics secrets as Kubernetes secrets, which I can then manage with a CI/CD pipeline and automate updates for.
Apache, Apache Lucene, Apache Hadoop, Hadoop, HDFS and the yellow elephant
logo are trademarks of the
Apache Software Foundation
in the United States and/or other countries.