vlsi opened a new issue, #6007:
URL: https://github.com/apache/jmeter/issues/6007
### 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_
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: dev-unsubscr...@jmeter.apache.org.apache.org
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
