Version Controlling Steps with Resource.json Files

After reading some of the other posts on this forum about the resource.json files contained within an Ignition project, I was wondering what the proper way to version control these items would be.

After pulling the most up-to-date version of a project on the gateway, should you enter the designer to "save", which could update the resource.json files? Or are they not updated when saving a project with no changes made directly in the designer?

The posts I've read give me some assurance that the presence of resource.json files is incredibly important, but how you would go about controlling them is a bit confusing.

Hey Alexander,

In 8.3 the issues for resource.json are greatly reduced. 8.3 is a lot more lenient on restoring the resource.json. You won't get the churn like you used to with 8.1. You can safely restore tracked resource.json without issue.

I only commit a resource.json if I made changes to the resource e.g. code.py, view.json, config.json. For newly untracked resources, you must commit resource.json or else you'll have a bunch of problems as mentioned across different posts on the forum.

Hope this helps!

Note that, depending on the resource type you're committing, there can be structurally significant changes in the resource.json attributes section. Make sure to double check both versions or you're going to have a bad time.

The gist of this is that as of 8.3 we're no longer writing back an updated resource.json file when we detect that the "last modification" attributes changed out from under us. Longer term, we're very interested in a more cohesive solution to separate that tracking metadata out of the actual resource signature, but it's not going to change in 8.3 or 2027 at least.