Enhanced DCM Handler Features

[Treyson]

We are using the DCM handler feature released in Alteryx 24.1 to help us manage our SDLC. We use the migration tool to move workflows from a dev to prod environment and then the handler manages the DCM connections between those two environments. In the dev Alteryx server all connections point to dev sources, and in the production environment all connections point to prod sources. This works well in RDBs because we just have both environments setup the same at a DB, Schema, Table level.

We have run into a situation with S3 buckets, where because S3 buckets have a unique global name, we can't have an S3 dev environment switch to an S3 prod environment. The S3 tool is wired to look for a very specific bucket name. If in the DCM handler, we could also map dev bucket names to a prod bucket name that also gets switched at run time, that would solve my problem.

In the meantime, we have to adjust the workflow migration tool to make those changes when the workflow moves from dev to prod.

Thank you,

Treyson Marks