Some checks failed
Deploy to Phoenix / deploy (push) Has been cancelled
- ADD_CHAIN138_TO_LEDGER_LIVE: Ledger form done; public code review repo bis-innovations/LedgerLive; init/push commands - CONTRACT_DEPLOYMENT_RUNBOOK: Chain 138 gas price 1 gwei, 36-addr check, TransactionMirror workaround - CONTRACT_*: AddressMapper, MirrorManager deployed 2026-02-12; 36-address on-chain check - NEXT_STEPS_FOR_YOU: Ledger done; steps completable now (no LAN); run-completable-tasks-from-anywhere - MASTER_INDEX, OPERATOR_OPTIONAL, SMART_CONTRACTS_INVENTORY_SIMPLE: updates - LEDGER_BLOCKCHAIN_INTEGRATION_COMPLETE: bis-innovations/LedgerLive reference Co-authored-by: Cursor <cursoragent@cursor.com>
4.2 KiB
4.2 KiB
Deployment Execution Status
Last Updated: 2026-01-31
Document Version: 1.0
Status: Active Documentation
Date: 2026-01-19
Status: ⚠️ PARTIALLY COMPLETE
Execution Summary
✅ Completed Steps
-
Scripts Created:
- ✅ DBIS Core Banking private offering seed script
- ✅ Admin vault provisioning service
- ✅ Admin vault provisioning scripts (TypeScript & Shell)
- ✅ Secrets migration script
-
Documentation:
- ✅ Admin Vault Setup guide
- ✅ Complete implementation summary
- ✅ Deployment execution status (this document)
⚠️ Issues Encountered
1. DBIS Core Banking Offering Seed
Issue: Prisma client connection error
Error: Cannot read properties of undefined (reading 'findUnique')
Cause: Database connection not configured or Prisma client not generated
Solution Required:
- Ensure database is running and accessible
- Set
DATABASE_URLenvironment variable - Run
npx prisma generateto generate Prisma client - Then run:
npx tsx scripts/seed-dbis-core-private-offering.ts
2. Secrets Migration
Issue: HTTP 307 redirects from Vault cluster
Status: Fixed in migration script with -L flag for curl to follow redirects
Action Taken:
- Updated migration script to handle redirects
- Script now follows redirects automatically
Current Status
DBIS Core Banking Offering
- Script: ✅ Created
- Status: ⏳ Pending database connection
- Next Step: Configure database and run seed script
Admin Vault
- Provisioning Service: ✅ Created
- Provisioning Scripts: ✅ Created
- Status: ⏳ Ready to provision (requires Vault access)
Secrets Migration
- Migration Script: ✅ Created and fixed
- Status: ⏳ Ready to run (requires Vault access and admin vault provisioned)
Next Steps
Immediate Actions
-
Configure Database for DBIS Core Offering:
cd dbis_core export DATABASE_URL="postgresql://user:password@host:port/database" npx prisma generate npx tsx scripts/seed-dbis-core-private-offering.ts -
Provision Admin Vault:
export VAULT_TOKEN=hvs.PMJcL6HkZnz0unUYZAdfttZY export VAULT_ADDR=http://192.168.11.200:8200 ./scripts/provision-admin-vault.sh -
Migrate Secrets:
export VAULT_TOKEN=hvs.PMJcL6HkZnz0unUYZAdfttZY export VAULT_ADDR=http://192.168.11.200:8200 ./scripts/migrate-secrets-to-admin-vault.sh
Verification Steps
-
Verify DBIS Core Offering:
# Check marketplace database # Query iruOffering table for 'DBIS-CORE-BANKING-PRIVATE' -
Verify Admin Vault:
vault list secret/data/admin/sankofa-admin -
Verify Secrets Migration:
vault list secret/data/admin/sankofa-admin/blockchain vault list secret/data/admin/sankofa-admin/cloudflare vault list secret/data/admin/sankofa-admin/npm
Files Created
Scripts
dbis_core/scripts/seed-dbis-core-private-offering.tsdbis_core/scripts/provision-admin-vault.tsdbis_core/src/core/iru/provisioning/admin-vault-provisioning.service.tsscripts/provision-admin-vault.shscripts/migrate-secrets-to-admin-vault.sh
Documentation
docs/04-configuration/ADMIN_VAULT_SETUP.mddocs/04-configuration/DBIS_CORE_ADMIN_VAULT_COMPLETE.mddocs/04-configuration/DEPLOYMENT_EXECUTION_STATUS.md
Troubleshooting
Database Connection Issues
If Prisma client fails:
- Check database is running
- Verify
DATABASE_URLis set correctly - Run
npx prisma generate - Test connection:
npx prisma db pull
Vault Connection Issues
If Vault operations fail:
- Check Vault cluster is accessible
- Verify
VAULT_TOKENis valid - Check cluster is unsealed
- Test with:
curl -H "X-Vault-Token: $VAULT_TOKEN" $VAULT_ADDR/v1/sys/health
Migration Issues
If migration fails:
- Ensure admin vault is provisioned first
- Check Vault token has write permissions
- Verify KV v2 secrets engine is enabled at
secret/ - Review error messages for specific issues
Status: ⚠️ READY FOR MANUAL EXECUTION
Last Updated: 2026-01-19