Academy / Week 2 / SyncApp Support Service / Provision Flow — Data Source Creation

Provision Flow — Data Source Creation

Lesson 8.5 ⏱ ~6 min Week 2

💡 Why This Matters

Data source creation is the step that generates the SyncApp's credentials (username, password, legacy ID). These are the identifiers used throughout the SyncApp's lifetime. Understanding how this is automated — and how it calls sync-app-authentication — connects the provisioning flow to the authentication service.

🎯 What You'll Learn

  • What 'create data source' means: generating a username, password, and legacy/adapter ID for the new SyncApp
  • How the adapter ID (legacy ID) is the last number in the source username — used in settings configuration
  • The createCloudSyncAppCredential function: inputs are PMS name, location ID, and SyncApp tag
  • What the SyncApp Tag is: the initial binary version to spin up (the SyncApp then auto-updates to latest)
  • How sync-app-support calls sync-app-authentication's Create method via an auth client
  • ACL 203 permission requirement for creating a data source

Watch Video

Open in Google Drive 💡 Open in Drive for AI-powered transcript search and summaries

📋 Lesson Summary

The createCloudSyncAppCredential function automates the data source creation step. It takes the PMS name, location ID, and SyncApp tag as inputs. The SyncApp tag specifies the initial version — the SyncApp will update to the latest version on its first 14-hour check. Internally, it calls sync-app-authentication's Create method via an auth client. The result is a username (source username), password (source password), and legacy/adapter ID (the last number in the username) — all of which are used in the SyncApp's settings configuration. ACL 203 is required for this operation.

🏷 Key Concepts

createCloudSyncAppCredential FunctionSource UsernameSource PasswordAdapter ID (Legacy ID)SyncApp TagInitial Binary Versionsync-app-authentication Auth ClientACL 203

Key Takeaways

01The adapter ID is always the last number in the source username — you'll need this when configuring settings.json
02SyncApp Tag controls the initial version only — always keep it updated when adding new integrations
03The auth client (sync-app-authentication) handles the actual data source record creation
04After this step, you have credentials to identify the SyncApp but no process is running yet
05If data source creation fails, check ACL 203 permissions and whether the location exists in WAM