Open sgreenbury opened 5 months ago
Quoting comments made by @penelopeysm below:
The versioning strategy feels quite tricky to get right. I think there is a correct answer, and I'm not sure if the below is it, but I hope it's not too far from it. Also I'll adopt Andy's names poppusher and popgetter because I think they are very sensible!
*** In theory, we could have separate minor versions for poppusher and popgetter to avoid republishing data due to this. i.e. instead of a one-to-one mapping between poppusher and popgetter, it would be a one-to-many i.e. multiple versions of popgetter can depend on one version of poppusher. I think this was what I had in mind when I wrote the current popgetter README. However revisiting this, I think the cognitive overhead of doing this is unnecessarily high, and it also makes it impossible to enforce the version invariants in code, which I think is a huge plus of keeping the version numbers in sync.
Placeholder for handling versioning of the pipeline data on Azure.