The lineage.json file is captured after the snapshot (since it depends on the snapshot to get the hashes). The file is deleted before the snapshot, so it will never show up in a restore. It is saved in the snapshot's lineage.
This might be unexpected to the user. In theory, we could copy the file from the snapshot lineage after doing the restore. However, it might not be necessary, as you probably won't care about the file in the exporting workspace. In the importing workspace, the file is considered part of the resource and captured as apart of the snapshots.
The lineage.json file is captured after the snapshot (since it depends on the snapshot to get the hashes). The file is deleted before the snapshot, so it will never show up in a restore. It is saved in the snapshot's lineage.
This might be unexpected to the user. In theory, we could copy the file from the snapshot lineage after doing the restore. However, it might not be necessary, as you probably won't care about the file in the exporting workspace. In the importing workspace, the file is considered part of the resource and captured as apart of the snapshots.