docs/setup/deploying-a-runtime: example of registering a runtime

[ptrus]

Fixes: #3081

TODO:

• depends on go/registry: Add support for querying suspended runtimes #3099
• add some documentation about "suspended runtimes" & runtime parameters
• figure out the best way to keep the fixture maintainable (maybe extend the "default fixture" command to support all the modifications needed - not sure)

[codecov]

Codecov Report

Merging #3100 into master will increase coverage by 0.21%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##           master    #3100      +/-   ##
==========================================
+ Coverage   67.21%   67.42%   +0.21%     
==========================================
  Files         371      371              
  Lines       36107    36107              
==========================================
+ Hits        24270    24346      +76     
+ Misses       8683     8631      -52     
+ Partials     3154     3130      -24     

Impacted Files	Coverage Δ
go/worker/common/p2p/dispatch.go	76.31% <0.00%> (-4.39%)	⬇️
...consensus/tendermint/apps/registry/transactions.go	56.16% <0.00%> (-1.65%)	⬇️
go/consensus/tendermint/roothash/roothash.go	71.75% <0.00%> (-0.85%)	⬇️
go/consensus/api/grpc.go	69.72% <0.00%> (-0.55%)	⬇️
go/consensus/tendermint/full/full.go	62.31% <0.00%> (-0.49%)	⬇️
.../consensus/tendermint/apps/registry/state/state.go	59.16% <0.00%> (ø)
go/worker/registration/worker.go	69.54% <0.00%> (+0.39%)	⬆️
go/consensus/tendermint/abci/mux.go	52.86% <0.00%> (+0.84%)	⬆️
go/worker/common/committee/group.go	79.24% <0.00%> (+0.94%)	⬆️
go/consensus/tendermint/abci/state.go	69.15% <0.00%> (+1.24%)	⬆️
... and 18 more

---

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 767c163...8c00e65. Read the comment docs.

[kostko]

If it's not tested periodically, it will rot.

[ptrus]

I fixed this by extending the default fixture command, and using that here instead of providing a separate json, which should be much better in terms of rotting, but still not perfect.

I think docs will generally tend to rot (specially the more low level ones) unless someone periodically goes over the docs and actually tries them out. Maybe adding a "make sure documentation is up to date" should be added to the process of creating major releases (as a manual step). However we do have quite a lot of docs already in this repository, so the exact step should probably be something like: "documentation owners" should make sure documentation is up to date with the version getting released - few days before releasing a new major version? ("documentation owners" - since it's probably a bit much for a single person to go over all).

edit: maybe a bit overkill for now, but in future we'll probably want something like this

[kostko]

Would be cool to get this merged.