Hello fellow Sdfers. Just wondering, it's quite of...
# sdf
s
Hello fellow Sdfers. Just wondering, it's quite often the case especially with large releases that deploy fails due to something which wasn't caught at validation. Like deploy.xml ordering, or duplicate script parameter ids for example. This causes some files and objects to get deployed, but others not when it fails. It would be amazing to have SDF rollback what was deployed in case of failure. 1. are there plans to introduce something similar? 2. would the new preview feature serve this purpose? 3. will validation be improved to catch deploy.xml resolve issues at some stage?
s
You're pain is felt by many of us. I feel the failures due to deployment ordering is quite unacceptable- IMHO that should be one of the main reasons to use SDF - it sorting out deployment order dependencies.
There has been some chatter on making SDF deployment atomic as well, but I don't recall any commitment in that direction.
p
If I could get one thing for christmas ☝️ ….. 😜
🎁 1
b
I haven't had a chance to explore this yet, but you might take a look at Salto. They claim to have tooling that help "map out dependencies", whatever that means.
👀 1
m
@Brendan Boyd thanks for sharing. It looks like a very interesting tool and the core components are even open source. It looks like they use SDF under the hood but have logic around it to handle some of the quirks/bugs. https://github.com/salto-io/salto/tree/master/packages/netsuite-adapter
👍 1
b
Ya, the same config language is used by terraform and is popular for for provisioning VM's and networking. It's basically terraform for Netsuite and Salesforce. Would be much better than working with xml IMO.
@Carlos Olivares (NS DevTools PM) you might find this project interesting too ☝️
s
I would prefer XML - if we had good schemas which we don't, so yes it's no better than JSON at this point.
p
@Brendan Boyd Thanks for the link, think I’ll request a demo
👍 1
s
@stalbert agreed, i think the current state of SDF makes fully automated deployments a pain without lots of manual logic to make up for its shortcomings. Main one for me being: • not all dependencies being added to manifest • deploy xml resolving issues • partial deploys in case of failure • deletion of scripts and files I'll consider opening a couple of tickets. == @Brendan Boyd always coming up with the goods. Thanks will look into it.