Overview
What is Recce Cloud?
Recce Cloud is a data collaboration platform for teams doing data validation, impact analysis, and pull requests reviews. It helps data teams catch issues early, understand downstream impacts, and communicate changes clearly—all in one shared workspace. Instead of working alone in a local dev environment, teams can explore lineage, run custom queries, and validate metrics together, speeding up reviews and building trust across stakeholders.
- Follow the Getting Started guide
Integration with GitHub
Recce Cloud integrates with GitHub to support validation in your PR workflow. The following instructions provide an overview of the setup. For a hands-on walkthrough, check out the Jaffle Shop Tutorial for Cloud.
Prerequisite
- Sign in Recce cloud
- Click Install button to install Recce Cloud github app to your personal or organization account.
- Authorize the repositories to the github app.
- Prepare the github personal access token with the
repo
permission. Please see the GitHub document. And set it to your environment variable. Or you can set the--cloud-token <GITHUB_TOKEN>
command option. - Prepare the Recce state password. The Recce state password is used to encrypt/decrypt the state file before uploading/downloading. The password is not stored in Recce Cloud, so you need to keep it safe.
Or you can set the
--password <password>
or-p <password>
command option.
Launch the recce server
in the cloud mode
- Create a branch for developing.
- Develop your features and prepare the dbt artifacts for the base (
target-base/
) and current (target/
) environments. - Create a pull request for this branch. Recce Cloud requires an open pull request in your GitHub repository. It also stores the latest Recce state for each pull request.
- Launch the Recce instance in the cloud mode. It will use the dbt artifacts in the local
target
andtarget-base
and initiate a new review state if necessary.
Note
Here we assume the you have set the GITHUB_TOKEN
and RECCE_STATE_PASSWORD
in your environment variables.
Review in the cloud mode
If the review state is already available for this PR, you can open the Recce instance to review.
- Checkout the branch for the reviewed PR.
- Launch the Recce instance to review this PR
Usage
All the commands requires the following settings.
Name | Environment Variables | CLI Options | Description |
---|---|---|---|
Cloud token | GITHUB_TOKEN |
--cloud-token |
Used for 1. Get the pull request from github 2. Used as the access token to the recce cloud |
State password | RECCE_STATE_PASSWORD |
--password |
Used to encrypt/decrypt the state in the recce cloud |
Recce Cloud is used for pull request reviews. Before interacting with the cloud state, you should switch to a branch that has an open PR on the remote.
Recce server
Initiate the review session of the PR. It would use the local dbt artifacts in the target/
and target-base/
directories to sync the state with the cloud.
Recce server (Review mode)
Review a PR with the remote state.
Recce run
Run or rerun the PR's checks and sync the state with cloud.
Recce summary
Generate the summary markdown
Recce cloud
The cloud subcommand in recce provides functionality for managing state files in cloud storage.
purge
You can purge the state from your current PR. It is useful when
- You forgot the password
- You would like to reset the state of this PR.
upload
If you already have the state file for the PR, you can upload it to the cloud.
download
You can download the recce state file of the PR from cloud as well.
GitHub Pull Request Status Check
Recce Cloud integrate with the GitHub Pull Request Status Check. If there is recce review state synced to a PR, the PR would has a recce cloud check status. Once all checks in recce are approved, the check status would change to passed and ready to be merged.