pyscitt needs to update to a supported CCF governance API

[achamayou]

There is logic in

scitt-ccf-ledger/pyscitt/pyscitt/governance.py

Line 4 in 474d31c

from typing import TYPE_CHECKING

and elsewhere that relies on the classic CCF governance API (i.e. pre-Azure compliance, pre-versioning).

See https://microsoft.github.io/CCF/main/governance/member_rpc_api.html for details of the governance APIs

I suggest reviewing the extent to which this dependency is necessary, and minimising the surface.

[achamayou]

Having reviewed https://github.com/microsoft/scitt-ccf-ledger/blob/main/pyscitt/pyscitt/governance.py, I am not clear on why pyscitt is wrapping the CCF governance API and exposing that in the CLI, the value seems minimal compared to letting ledger operators use ccf_cose_sign1 directly?

[ivarprudnikov]

Public API is: submit,retrieve,pretty-receipt,embed-receipt,validate,split-payload which is defined in pyscitt/pyscitt/cli/main.py
Everything else would be used for testing purposes only. We need to be able to run the functional tests at the end of the day.

• run-dev.sh is using governance, i.e. scitt governance local_development. It is used to start the local ledger to test against when running run_functional_tests.sh
• Both demos use governance API in the examples