Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Why is validation_definition_store_name not part of the great_expectations.yaml spec? #10958

Open
CrossNox opened this issue Feb 21, 2025 · 0 comments

Comments

@CrossNox
Copy link

I'm trying to set up GX in such a way that I can use a single yaml to run both production and development environments.

On config_variables I have env for this purpose. Then, e.g. expectations_store_name could be ${env}_expectations_store, with dev_expectations_store and prd_expectations_store configured as Filesystem/S3 backends, respectively. The S3 backend could be populated on CI.

But now, what should I do with the validation_definition_store ?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant