When updating a resource should the user specify the version or should it auto-increment?

[jrschumacher]

When working on the CLI we found that the version needs to be updated with every update. Is this expected behavior?

https://github.com/opentdf/tructl/pull/4/files#r1454199592

[strantalis]

I mentioned version here but I think unless we plan on tracking policy config changes we should just remove the concept of version for now imo.

[jakedoublev]

It sounds like there are probably two different types of versioning of a resource (unless I'm misunderstanding):

1. customer creation (v0 or v1) and then customer-driven updates to the created resource (v2, v3...)
2. Virtru-driven changes to schemas requiring migrations (which I understand there are general roadmap plans around to improve UX)

I'm guessing we only care about the 1st in this discussion because migrations (when needed) will tied to the version of the DSP itself (and therefore all resources within) and no transitive state or backwards compatibility support will be needed if we have control over the migrations themselves? Is that thinking correct?

[jrschumacher]

Versions were determined to be irrelevant to the actual platform and rather something to track OCI. This will be done via Metadata.Labels.