Anyone interested in collaborating on an automation to check the difference between a commit/hash and a NetSuite instance? I know all the features are there, just want to put together a node package that can execute the steps in Webstorm and present the user with changes window that can then allow for those changes to be committed to the repo.

So you're using NetSuite as a repo to pull into your own repo?

No. What I mean is ... if I PULL from NetSuite onto everything that is in my repo project, I'll be able to see any config and/or code changes that a user may have done. If I merge that back to my repo, I can ensure I retain those changes before I do my next sdf deploy

Basically doing an "update objects from account..." and then checking which files has changed in the commit pane?

I guess my point is the user shouldn't have been doing anything that isn't committed to your repo/sdf project. Its a bit weird to pull in random user changes. You can def do this with something like beyond compare though if you want to do some kinda diff. I'm not sure what node flavors there are but it doesn't seem like an unreasonable thing.

Sounds like Darren is trying to automate something like https://stoic.software/sustainable-suitescript/suitescript-operations-environmental-drift/

@michoel, that's precisely it yes. I had a long discussion with Eric on this topic. So, who's in?

I would like to be able to deploy a single file that I use as a common library for every account we have, then I send the current code to the sandbox and production of the current project. Common file -> All accounts Current project -> Sandbox and Production

I've thought about doing something like this and have the beginnings of a bash script. You might also take a look at this project: https://github.com/salto-io/salto