CLI deploy: project starts to diverge with itself

[josephjclark]

Seeing a problem in v2 deploy

• Pull a project
• Edit it
• Deploy it - all OK
• Edit again
• Deploy it - divergence error

This is weird - I'll have to investigate and find out where that divergence is coming from

High priority

[josephjclark]

Would be super helpful to console.log a json diff of the two workflows when a divergence is detected

[josephjclark]

The problem might be that a trailing line break is getting appended to the job expression somewhere

[josephjclark]

Found it

When we finally deploy the project, we take the version history returned to us by the provisioner API, and save that locally for the next deploy.

But the provisioner returns us an out of date history!!

So the local history we then check next time is wrong, and it looks like the server has diverged

A workaround (which I'll release immediately) is to deploy the changes, then refetch the project, then use the history in the refetched version

See Lightning: OpenFn/lightning#4455