What's your method for resolving resource.json git conflicts?

  1. All new resources you create end up in the repo without a corresponding resource.json. So when you push / clone the repo to a new system Ignition will not recognize (in some cases even delete) the new files.
  2. I can not answer this, but I would expect it.
  3. No, it only creates a new valid signature. The packing / unpacking mechanism has to be done in git hookscripts (which use the helper tool to create a new signature). Not a perfect solution for sure, but let's wait and see what Ignition 8.3 brings us :slight_smile: