Learn how to test Sequin locally and in CI to verify configuration, transforms, filters, and end-to-end connectivity
sequin.yaml
file for your sinks that you want to test. This is used to programmatically configure Sequin in test environmentssequin_test
user with replication privileges.sequin.yml
as your test configuration. This ensures that your current dev configuration is properly tested without needing to update a separate sequin.yml
file.For instance, you can use environment variables in yoursequin.yml
to create:Test
accountTEST_API_TOKEN
for use in your testssequin_test
user.
create_if_not_exists: true
flag.sequin config interpolate
command to preview your sequin.yml
file after environment variables are interpolated. This will help you catch any issues with your environment variables.docker-compose.test.yml
(or helm, etc.) file that includes all the necessary services to run Sequin in a test environment. This should include the Sequin service and it’s dependent Postgres and Redis services. A couple considerations:sequin.yml
configuration file:
TELEMETRY_ENABLED
environment variable to false
.
sequin.yml
file as you’ll run in production - but use environment variables to properly configure your database connections and sinks for your CI environment.A couple considerations in CI:sequin config interpolate
command to preview your sequin.yml
file after environment variables are interpolated. This will help you catch any issues with your environment variables.sequin.ci.yml
configuration file:
TELEMETRY_ENABLED
environment variable to false
.
/health
endpoint is returning a 200 status code.