Great Expectations
An overview of the Great Expectations integration with Secoda
Last updated
An overview of the Great Expectations integration with Secoda
Last updated
Secoda currently supports retrieving expectation and validation metadata from Google Cloud Storage and AWS S3.
There are two steps to get started using Great Expectations with Secoda through Google Cloud Storage:
Create a service account for Secoda
Connect Google Cloud Storage to Secoda
To provide least privilege to Secoda for extracting Big Query metadata, you can create a new service account following the steps below. Refer to Google Cloud’s documentation about service accounts for more information.
From the Navigation panel on the left, go to IAM & admin > Service accounts
Click Create Service Account along the top
Enter a name (for example: “secoda”) and click Create
When assigning permissions, make sure to grant the following roles:
5. Create a JSON key. The downloaded file will be used to create your warehouse in the next section.
Log into your Secoda profile at https://app.secoda.co
From the Navigation panel on the left go Integrations > Add new integration
Select Great Expectations and fill in the fields based off of the Great Expectations configuration YAML file.
Make sure to upload the Great Expectations configuration YAML file.
You will be asked to map each datasource outlined in your configuration file to an existing integration in Secoda.
There are two steps to get started using Great Expectations with Secoda through AWS S3
Create a new AWS IAM user
Connect AWS S3 to Secoda
You can create an IAM user using one of three methods:
Note: Ensure that Access Key - Programmatic Access is checked.
Once you create the user you can save the Access Key ID and Secret Access Key generated for the user.
Attach the following policy to the newly created user. Make sure to change <your-bucket-name>
Log into your Secoda profile at https://app.secoda.co
From the Navigation panel on the left go Integrations > Add new integration
Select Great Expectations and fill in the fields based off of the Great Expectations configuration YAML file.
Make sure to upload the Great Expectations configuration YAML file.
You will be asked to map each datasource outlined in your configuration file to an existing integration in Secoda.