This article provides an overview of the weekly synchronization process between the production and staging, including the sync rules applied during this process.
The synchronization keeps the staging environment closely aligned with production for accurate testing, while allowing the development environment to be synced as needed for specific projects.
Sync schedule
- Frequency: Every Saturday at around 3 AM AEST
- Source: Production → Staging
Sync Process
During the sync, all data in staging is overwritten with a copy of production data that has been anonymized to protect privacy. This ensures staging accurately reflects production while maintaining data security.
Sync rules
- All product and order data on staging will be overwritten by anonymized production data.
- User credentials will be copied from production to staging. Users should use their production credentials to access the staging environment.
- API Keys will be copied from production to staging.
- Webhooks on staging will be wiped clean. However, webhooks from production will not be transferred to staging to prevent any inadvertent data transmission.
- MConnect integration setup on staging will be cleared and must be manually set up again.
Sync rules for anonymization
In anonymizing a Marketplacer database, synchronization rules dictate the transformations applied to its tables and columns. These rules guarantee the replacement or removal of personally identifiable information or sensitive data, preserving privacy while upholding data integrity.
Notes
- Custom sync cadences are not currently supported.
- Any data that exists only in staging and not in production will be removed during the sync.
- Webhooks can be re-created automatically after the sync using the Marketplacer API. For detailed instructions on this, refer to Manage Webhooks guide.
Related articles