Provision Flow — Add Settings & Spin Up SyncApp
Why This Matters
The final two steps — injecting PMS settings into WAM and spinning up the SyncApp pod — complete the automation chain. Understanding how settings.json is created from the provisioner configuration, and how Kubernetes differs from local execution, will help you debug provisioning issues in production.
What You'll Learn
- How the createDentalEMRSyncApp method (or equivalent per PMS) sets EMR settings and spins up the SyncApp
- The two components needed to spin up a SyncApp: settings.json and the SyncApp binary (on laptop) or pod (in Kubernetes)
- How PMS-specific settings (e.g., DentalEMR practice ID) are injected into WAM location settings programmatically
- The difference between local execution (your machine = the system) vs Kubernetes (a pod = the system)
- What 'spin up a SyncApp' means at the Kubernetes level: creating a pod with the settings configuration
Watch Video
Lesson Summary
The final provision steps inject PMS-specific settings into WAM and launch the SyncApp. The createDentalEMRSyncApp method (or PMS-equivalent) has two parts: set EMR settings (PMS credentials written to WAM location settings) and create cloud SyncApp (spin up the pod using all collected configuration). On a developer's laptop, this runs as a local process with settings.json; in production, Kubernetes creates a pod. Once complete, the SyncApp is running and will begin its first sync cycle.