Support overriding test element properties from user.properties #6007
Description
Use case
There might be a need to override some of the properties based for a specific environment, or for a specific test launch.
Currently, users can manually put ${...} expressions, however, they do need to provision the expressions in advance.
Possible solution
Implement a naming convention so users can craft properties that override values in the components.
For instance: components.<component-id>.<subcomponent-id>.<subcomponent-id>.<property-name>=<property-value>
Open questions:
- Do we need to have a stable component ids or can we rely on the names?
- How do we handle "collection" properties? For instance, should be have separate syntax for "add", "remove", and "replace" operations?
Possible workarounds
No response
JMeter Version
5.6
Java Version
No response
OS Version
No response