Cargo registry service for deploying programs

[pgarg66]

Problem

Need convenient mechanism to hook up cargo publish command for on-chain program. The users should be able to deploy programs to the blockchain using cargo publish.

Summary of Changes

This PR implements a custom Cargo registry service. It provides a registry endpoint for cargo commands, and uses Solana's RPC client to interface with the blockchain.

Steps to use the service

Optionally, run the test-validator

Run the service

1. Generate keypairs for payer and authority accounts.
2. Fund the payer's account (e.g. airdrop if using test-validator).
3. Start the server

solana-cargo-registry -a authority.keypair -k payer.keypair -u <rpc endpoint URL> -p <available local TCP port>

Update on-chain program's cargo.toml

Insert following under [package] section of the toml file.

include = [
    "**/*.rs",
    "out/**.so",
    "out/**.json",
    "Cargo.toml",
]

Update cargo config file to add the registry

Create (or update existing) .cargo/config by adding the following. <server-port> must be replaced with <available local TCP port> value from solana-cargo-registry command.

[registries]
my-registry = { index = "http://0.0.0.0:<server-port>/git" }

[net]
git-fetch-with-cli = true

Build on-chain program

1. Build the on-chain program for sbf-v2 arch.
2. It's important to generate the output to ./out/ folder for now.

cargo build-sbf  --sbf-out-dir ./out/ --arch sbfv2

One time login to the registry server

cargo login --registry my-registry

When prompted for access token, just enter any string.

Publish the program

cargo publish --registry my-registry

[codecov]

Codecov Report

Merging #33570 (4d85196) into master (c588f25) will increase coverage by 0.1%.
The diff coverage is 50.0%.

@@            Coverage Diff            @@
##           master   #33570     +/-   ##
=========================================
+ Coverage    81.7%    81.9%   +0.1%     
=========================================
  Files         807      807             
  Lines      218283   217911    -372     
=========================================
+ Hits       178485   178490      +5     
+ Misses      39798    39421    -377     

[Lichtso]

Looking very good over all!

Is GIT used for the fetch API? I thought we wanted to implement the sparse protocol instead.

[pgarg66]

Looking very good over all!

Is GIT used for the fetch API? I thought we wanted to implement the sparse protocol instead.

Yes, still planning to use sparse index. GIT index is a placeholder for now. An index implementation was necessary for publish command handling. And, GIT based implementation is better documented.