The Meroxa access token is needed to authenticate to the Meroxa API programmatically. For example, the token allows you to build pipelines with Terraform.
To obtain a token, you must install the Meroxa CLI. Then, follow these steps:
- Log in to the CLI.
$ meroxa login
- Get token.
meroxa config command allows you access details about your Meroxa environment.
For security, the output is obfuscated unless you use the
$ meroxa config --json
If you're familiar with
jq, in one command, you can parse the JSON output and only print the Meroxa token:
$ meroxa config --json | jq -r .config.access_token
You could also add this to your
.profile to always have it available in your environment.
export MEROXA_REFRESH_TOKEN=$(meroxa config --json | jq -r .config.access_token)
In this guide, we will create a real-time data pipeline to create a delta table in BigQuery of changes from a PostgreSQL database using Meroxa. This pipeline will create, store, and update a table within BigQuery that contains a row for every insert, update, and delete operation from PostgreSQL.
In this guide, we are going to create a real-time data pipeline to sync data from PostgreSQL to Redshift using Meroxa. This pipeline will keep a table within Redshift up-to-date with every insert, update, and delete operation from PostgreSQL.
For this example, we are going to use ngrok. ngrok exposes local servers behind NATs and firewalls to the public internet over secure tunnels.