Orchestration versioning is challenging in the current implementation (as of v0.5.0) for a couple reasons:
The DB schema doesn't currently expose DTFx version information, making it difficult to implement version-specific logic within an orchestration. More context on orchestration versioning can be found here.
Task hub names are not explicitly configurable, so side-by-side deployment strategies with a shared database for versioning require new credentials to be configured.
This issue tracks the work required to simplify versioning when using the SQL backend in DTFx.
Orchestration versioning is challenging in the current implementation (as of v0.5.0) for a couple reasons:
This issue tracks the work required to simplify versioning when using the SQL backend in DTFx.