Problems with automated deployment due to repo structure about extension-data-driven-parameters HOT 3 CLOSED

Hi @kabelak,

I've changed the trex file to be for all v2 updates (DataDrivenParameters_2.latest.trex) that way you can just pull that one file and won't have to change it for minor updates. Does this help with your situation?

Take care,
Keshia

from extension-data-driven-parameters.

Hi @KeshiaRose,
It's better in some ways, but still doesn't match the way the other repos work. the requirement to copy the .trex to a folder called 2.latest, which I assume would change with versions, is still a challenge for automated deployments. I appreciate there may be requirements, and if so, apologies, but having a single .trex populated with a static folder structure, would be awesome.

eg:
https://tableau.github.io/extension-data-driven-parameters/2.latest/#/parameter
v/s
https://tableau.github.io/extension-parameter-actions/#/paramact

from extension-data-driven-parameters.

Hi @kabelak,

I see, the most I can say is that I won't be updating from v2 for quite some time so your automated systems should be fine. Besides, and any major version number updates will include breaking changes.

Take care,
Keshia

from extension-data-driven-parameters.