How do we handle parameterless I/O snaps, like Reltios?

Some snaps have accounts that seem to not be able to be parameterized. Reltio is one that has the additional problem of a tenant URL that must be setup. It doesn’t seem to accept pipeline parameters, or even variables in the dataflow, for the tenant URL. How can we go about deploying such things?

The preferred method is to have an environment instance that has environment appropriate values, like accounts, features, technologies, that the newly deployed objects simply use. That might be fine in the perfect case of having different instances, but some things can still be a problem.

Still, how can we handle things like the tenant, which is currently part of the pipeline that would be deployed?

Steve