Colons are unsupported in pipeline parameter values
Created by: TokyoQ
The current implementation tokenizes the input with a colon delimiter and drops everything after it, so you can't set a colon in either the key or value.
e.g.
--variables START_TIME:05:50pm
sets START_TIME = 05 instead of 05:50pm
I'd suggest treating the first colon as the separator and taking everything following as the value.