Used update writable to update script files - how to stop the update?

[solgaeDK]

With App Volumes updated to 2.14, I re-created the group-based writable based on the new writable template. When I tested with a new login, which creates a new writable, I noticed that it also applies the update zip that I used previously to update the snapvol.cfg file. The snapvol.cfg update is no longer needed, but I can't find a way to stop the update. Any ideas?

[LarryBlanco2 · Accepted solution]

I had the same issue.  There is no way to set it to nothing once something is there.   For the point in time I did not need anything I just put in an empty zip file.    Seems the developers would have a use case where an update is no longer needed to be applied because of version changes or upgrades.   They should put in a method of removing the update from being applied.

Larry

[Ray_handels]

Agreed. The way it works now is you can only have 1 zip file that updates the writable. So if you have new version you will always need to also put in the old files you want to change.

[solgaeDK]

Thanks - I put in a zip file with one placeholder text file (just to confirm the "update" works as expected) and that did the job. Really, though, there should be an option to stop the updates...