The lack of any reasonable CICD processes is a major thorn in my client’s side and makes every deployment of changes a complex and risky endeavor. As such, we were happy to see some small steps toward addressing this need with the introduction of the object mappings in Configuration Hub (thanks @yael_kadoshi !).
I’ve been playing around with this new feature, and understand the basics, but there is no documentation around – and quite likely no functionality yet for – anything but the most basic JSON mappings. I’m wondering, for example, if anyone knows whether the following can be achieved:
Wild card for “Source Value”. (I tried an asterisk which didn’t work). For example, to be able to set all workflow “$.owner” values to the same service account target value, irrespective of the source owner value.
How to handle space characters in JSON paths? For example, we have some workflow steps like “Get Account”, and I wasn’t able to get that path understood with or without quotes (i.e. $.definition.steps.“Get Account”.defaultStep). For step names that don’t have a space, the same path format is working correctly.
Wondering if anyone has figured out any tips or tricks for using this Configuration Hub Object Mappings feature… Thank you!
Hi Alex,
Regarding CICD - we are continuously working to enable more APIs for configuration hub actions, such as: scheduling backups, drafts and deployments via APIS. We did publish following config hub APIs:
about object mapping:
Unfortunately, we currently do not support wildcards, but, would be happy to look at this as enhancement if this is needed, if you can create an idea suggestion.
To define a path that contains white spaces (or any special character) the correct notation is [‘property’] i.e. $.definition.steps.[‘Get Account’].defaultStep