How tritondatacenter/sdc-papi works
Project type and purpose
• sdc-papi is a standalone Node.js microservice within the Triton Data Center ecosystem.
• It exposes an HTTP/REST interface (“Packages API”) for creating, listing, and managing software packages used during OS provisioning.
File structure
• Top‐level artifacts
• server.js – entry point, spins up the HTTP server
• lib/ – core modules (backend logic, PAPI routes, tools, migrations, validations)
• etc/config.test.json – configuration for test environments
• smf/manifests – SMF service definition templates for Solaris zones
• deps/ – vendored scripts and linters
• test/ – integration tests and test harness scripts
• Jenkinsfile, Makefile, tools/ – CI/CD and development utilities
• Pattern hints
• Modular separation: routing (lib/papi.js) vs. business logic (lib/backend.js) vs. migrations & validations
• Deployment via SMF manifests and config scripts under boot/ and smf/
Extract README insights
• The service runs in its own VM (the “PAPI VM”) and is tested end‐to‐end with runtests.
• It integrates with Triton’s global headnode for sample data setup.