Forum Discussion
@mbowen Hi Matthew. I hope you are well. Earlier this summer you offered me a solution to get past my XML HTML entity declaration issues. We basically Base64 encoded the value of the XML element that contained my HTML entity codes, passed it through the both the XML Generator and XML Formatter snaps, and then just before we wrote the XML document to file, we used a Mapper snap with the following expression in it.
$content.replace(/<(short|long)-description>(.+?)</\1-description>/g,
(_matched, prefix, b64enc) => “<”+prefix+“-description>”+Base64.decode(b64enc)+“</”+prefix+“-description>”)
I now have another element in the same XML document that I wish to do a Base64.decode() on, however, I’m having trouble understanding how your replace method and the callback function within it works. Could you help me to understand it so that I can string an additional replace on this same expression?
I’m basically trying to decode the value of the custom-attribute below, but when I try to emulate the pattern that you established, I can’t get it to work.
<custom-attribute attribute-id="productFeatures">PCFbQ0RBVEFbPHA+RmVhdHVyZXMgTGlzdDwvcD5dXT4=</custom-attribute>
Hey @alex.panganiban.guild . Hope you’ve been well too. I will look at this today.
Thanks! As far as automating moving pipelines across environments, is the only thing we can do is using the Management API?
- stevegoodwin7 years agoEmployee
You can write pipelines using the snaplogic metadata snap pack to list, read, create, update assets.
This allows a user to create their own CI/CD workflow
Related Content
- 3 months ago
- 4 years ago
- 4 years ago