We manage our pipelines with automation, so I wanted to have our teams set a
dag value in our automation kit, and pass that value down to the steps definition on processing. This worked as expected when the end result was
dag: true, but if the end result was
dag: false we would get an error back from the API saying
["dag must be a boolean"]
I spent awhile making sure that I was indeed passing down a boolean, but I was able to manually confirm this by forcing
I’ve been able to work around the issue by updating our automation kit to simply not add dag if it is false, but it took me most of an afternoon to iterate and figure that out.