[Enhancement] Support Defining Params for Scripts

[BenB196]

Feature summary

Support the ability to define params in the script recorder.

Why is this feature important?

Currently there is no way to leverage params within the recorder. It would be nice to have the ability to define params within the recorder that could be used during the recording. These parameter values would just exist at the recorder level, and wouldn't be passed to the exported config.

If I want to log into a website, currently the recorder would capture my password in plaintext. This is less than ideal. Ideally, I should be able to specify a param for the password in the record (params.password), then the recorder would set the value of the password field to the param. Then for the actual deployment of the script, I could have the password value exposed as an environment variable in the container (MY_PASSWORD=password123), and then pass that environment variable to the param:

params:
  password: ${MY_PASSWORD}

Linked resources

No response

Additional information

No response

[drewpost]

Hi @BenB196 - thanks for the feedback. I agree that this (along with a number of your other suggestions) would be very useful. These capabilities are at the top of our backlog. Right now our 1.0 feature set is locked so these will be added in post 1.0.

[louisong]

@drewpost Customer has the following feedback:

User already download 1.1.0 from github relases for synthetic recorder and issue havent solved.
The version installed for synthetics recorder is 1.1.0 which referred by elastic, shows the password in the uploaded node js script.

---

Right now our 1.0 feature set is locked so these will be added in post 1.0.

Do we know (rough estimate) in which version release would this feature land?