Inventory
Record every endpoint, credential, printer, content format, option, status dependency, and retry policy your current integration uses.
PrintNode migration
Change the print path without betting the operation.
Piqae supports a migration-critical subset of the PrintNode printing API. Use that compatibility to canary deliberately—not to assume every historical behaviour matches.
Compatibility envelope
| Surface | V1 posture | Migration action |
|---|---|---|
| Computers / nodes | Migration-critical subset | Map identity and online semantics |
| Printers | Migration-critical subset | Re-resolve IDs from enrolled agents |
| Print jobs | Migration-critical subset | Test request and state fixtures |
| whoami, ping, noop | Covered subset | Run client health checks |
| Scales | Not claimed | Keep existing path or build separately |
| Integrator subaccount APIs | Not claimed as compatible | Map to Piqae workspaces explicitly |
| Historical response quirks | Not universally replicated | Fixture-test your exact client |
Scope reflects the checked-in V1 execution ledger. PrintNode’s original API is documented at printnode.com. Verified 29 July 2026.
Migration runbook 01 02 03 04 05 06
Map
Compare those behaviours with Piqae’s tested compatibility matrix. Treat gaps as explicit work, not assumptions.
Prepare
Enroll a separate agent, map printer identities, create scoped credentials, and define success and rollback thresholds.
Canary
Route a bounded, non-critical job set. Compare API responses, native queue results, webhooks, and operational recovery.
Expand
Increase traffic in stages while preserving the old base URL and credentials for immediate rollback.
Close
Retire the prior path only after a complete operating cycle, incident drill, and evidence review.
Rollback contract
Define “stop” before the canary begins.
- Keep the prior base URL and credentials available during the migration window.
- Stop expansion on duplicate risk, unexplained uncertainty, or unsupported driver options.
- Never automatically reprint an ambiguous job while rolling traffic back.
- Record the final disposition of every canary job across both systems.