How do I provision a party?
Table of Contents
The party stage on its own — the last stage of a full system provision,
for when the tenant is already active and you only need to provision a
root operational party. Tangled into the library as
party_provision.ores.
1. Question
How do I provision a single root operational party from the shell?
2. Answer
Log in as the tenant admin and provision party: the starting point's
party step publishes the reference data the party works from, activates
the party, marks its onboarding complete, and joins the administrator
who asked to it. The party is named by its exact full name (or UUID);
BARCLAYS PLC is the GLEIF root from the Barclays flow. The
counterparties a party works against are the tenant's and are published
once by the tenant's starting point, not here.
connect $ORES_NATS_URL login tenant_admin@barclays_plc Secure-Password-123 provision party "BARCLAYS PLC" logout exit
./ores.shell ${log_args} ${connect_args} << 'EOF'
<<party-provision>>
EOF
3. Script
projects/ores.shell/scripts/library/provisioning/party_provision.ores — generated
from this recipe by compass build --direct tangle_shell_scripts (do not
edit the .ores by hand).
4. Tested by
Manual: compass shell -f party_provision.ores after the tenant stage.
5. See also
- How do I provision the system with Barclays (GLEIF)? — the full flow.