A simple tool for working with production data in your local environment

Payload is a simple tool for working with production data in your local environment.

What problem does it solve?

You’re working with Cloud SQL in production, but you want to avoid connecting directly (or through cloud_sql_proxy) to your production database lest you accidentally run some destructive commands, or expose customer data. Both of which are considerd bad practice.

payload allows you to export the production database, trim customer data — such as by truncating users or running other SQL cleanup commands — before downloading the data to your machine and loading it into your local database for testing/local development.

Or you need to inspect real customer data, in which case you can use IAM to grant permission for a given engineer to a specific customer scope, which will not be cleaned up in the export.

This has some neat usecases:

  • Test upcoming database migrations against real data
  • Help debug customer issues without connecting to production
  • Run analytics against production without interfering with real data or running replicas
  • Create personal staging environments with real data so that you don’t need to manage large collections of seed data that invariably becomes unmaintained

View Github

Leave a Reply

Your email address will not be published. Required fields are marked *

This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.

GIPHY App Key not set. Please check settings

Live From INTERACT: Microsoft’s Developer Velocity Research

We’re Tracking 270 State-Sponsored Hacker Groups From Over 50 Countries