Purpose of sync-app-support
Why This Matters
Before diving into the provision code, you need to understand exactly which manual steps SyncApp Support automates. This mental model helps you understand what to look for when the automated flow fails.
What You'll Learn
- The manual SyncApp creation steps that sync-app-support automates: get location ID, PMS name, credentials, validate, create data source, configure settings, spin up
- How the provision metadata API works: lists all available PMS integrations and their required fields
- The provisioner map: how each PMS registers its provisioner using addProvisioner in register.go
- The field types for PMS credentials: string, password, and unknown
- The structure of a provisioner: Name, Metadata, Provision, Steps methods
Watch Video
Lesson Summary
SyncApp Support automates the entire manual provisioning sequence: (1) get location ID (still manual), (2) get PMS name and credentials, (3) validate credentials, (4) create data source, (5) add settings, (6) spin up SyncApp. The provision metadata API returns a list of all registered PMS integrations with their required fields. Each PMS registers a provisioner in register.go using addProvisioner. The provisioner implements Name, Metadata, Provision, and Steps. Integration partner codes are auto-incremented integers (e.g., DentalEMR = some number, next PMS = that number + 1).