Thank you for reaching out, and sorry to hear you are having trouble with empty structured configuration variables within your deployment process, but I would be happy to help take a closer look at things!
As an initial step, I found this really great forum post by one of my colleagues that seems to speak to the same use case, so I wanted to link this for your reference/review (in case you hadn’t come across this yet):
Thank you for the update, and I’m happy to hear you were able to get things going!
The behavior here does seem a little unintuitive, so I’ve reached out to our development team for clarification on the expected functionality for null and "" values when using the JSON structured configuration variables feature, and hopefully they can shed some light on this and whether or not it should be considered a bug in how this substitution currently works.
Thanks for your patience while I wait to hear back from the team on this, and let me know if I can be of any other help in the meantime.
Just stepping in for Britton with an update from the devs.
They are looking into ways to best accomodate this and it seems like there could be add an additional variable filter for setting null values using our Octostache library to provide a filter for the replacement.