Distribute migration reports to a central location/URL

[jribbink]

Issue to be solved

In order for tooling to query the status of the last migration report, there must exist some central server/URL which hosts so that the latest migration report can always be found.

(specifically needed for onflow/flow-cli#1508)

Suggested Solution

Setup a pattern for uploading these to GCP, GitHub, or other so that they may be repeatably queried by tooling & the latest report will always be used.

[jribbink]

I think we can probably just use GitHub for this & put the reports in this folder somewhere:

https://github.com/onflow/cadence/tree/e020944c7f187de8bf9bfc3b3293f32abb05510a/migrations_data

As long as we follow the same pattern each time, the CLI should be able to pick these up.

I'm thinking something like:

https://github.com/onflow/cadence/tree/master/migrations_data/raw_data/MM-DD-YYYY-NETWORK-TIMESTAMP.json

Where the CLI can choose the latest JSON (based on filename) for the given network of their choosing

[jribbink]

I've created the PR for the CLI to fetch contract update statuses for the latest migration report onflow/flow-cli#1529.

Currently, the CLI assumes the following:

• master branch of onflow/cadence
• files live in migrations_data/raw/XXXXX-NETWORK-<unix-timestamp>.json (naming can be anything as long as it ends with NETWORK-<unix-timestamp>.json)

If an alternate format is preferred, I can update the PR accordingly. If this is acceptable we can try to merge this Flow CLI PR ASAP. I can't seem to find the JSON report for the last emulated migration, so I'm unable to make a PR for this myself, but if someone else could do this that would be awesome.

Thanks!

(cc @j1010001 )

[jribbink]

closed by #3273