Although never documented, it seemed that I we update response body, the reponse template from provision should be also updated, but not. The current behavior takes always the provision responseBody as unvariable reference even if some transformation steps added new data or changed something.
But it is more intuitive, and indeed useful, to have the provision template as a start reference but evolving it with further transformation updates.
So, we shall modify the current behavior to enable this behavior and update documentation for it:
"As the transformation steps modify this data container, its value as a source is likewise updated."
Also, new play-h2agent example shall be added to leverage this property.
Although never documented, it seemed that I we update response body, the reponse template from provision should be also updated, but not. The current behavior takes always the provision responseBody as unvariable reference even if some transformation steps added new data or changed something. But it is more intuitive, and indeed useful, to have the provision template as a start reference but evolving it with further transformation updates. So, we shall modify the current behavior to enable this behavior and update documentation for it: "As the transformation steps modify this data container, its value as a source is likewise updated."
Also, new play-h2agent example shall be added to leverage this property.