fivetran/Great-Expectations-Data
Use Great Expectations https://docs.greatexpectations.io/en/latest/ to validate data.
View on GitHubTrust Signals
- Scorecard Score
- not yet scored
- Maintenance Recency
- Stale
- License
- None
Inputs
| name | description | required | default |
|---|---|---|---|
| CHECKPOINTS | A comma separated list of checkpoint names to execute. Example - "checkpoint1,checkpoint2" | — | — |
| NETLIFY_AUTH_TOKEN | A personal access token for Netlify. | — | — |
| NETLIFY_SITE_ID | A Netlify site id. | — | — |
| GE_HOME | Path relative to the root of your repository where the great_expectations directory exists. If not supplied defaults to the root. | — | — |
| DEBUG | Setting this input to any value will allow the Action to exit with a status code of 0 even if a checkpoint fails. This is used by maintainers of this Action for testing and debugging. | — | — |
Outputs
| name | description |
|---|---|
| ACTION_DOCS_LOCATION | The absolute path where generated data docs generated by the Action run are located. This is useful if you want to deploy the data docs to an external service. |
| FAILING_CHECKPOINTS | A comma delimited list of failed checkpoints. This will be an empty string if there are no failing checkpoints. |
| PASSING_CHECKPOINTS | A comma delimited list of passing checkpoints. This will be an empty string if there are no passing checkpoints. |
| NETLIFY_DOCS_URL | The url to the generated data docs on Netlify. This output is only emitted only if the input parameters NETLIFY_AUTH_TOKEN and NETLIFY_SITE_ID are provided. |
| CHECKPOINT_FAILURE_FLAG | This will return 0 if there are no checkpoint failures and 1 if there are one or more checkpoint failures. |