Is your feature request related to a problem? Please describe.
In SE we take rules_df as an input for SE and user need to build the rules_df. Along with this, if we can also have a base format YAML configuration for providing rules and users can maintain the file in the repository and provide the path in the SE configuration, rules_df has to be built by default.
Describe the solution you'd like
Add new argument while instantiating with_expectations to provide rules_yaml_path or rules_df {}Describe alternatives you've considered{} We had rules_table earlier which we removed as it is not generic. Having a YAML in the repository would be a generic native solution, but users will still have autonomy on bringing their own rules_df if needed. This should be a new plugin that takes in different file formats. We want to standardize it to YAML, but it should have flexibility to extend to json etc.
Is your feature request related to a problem? Please describe.
In SE we take rules_df as an input for SE and user need to build the rules_df. Along with this, if we can also have a base format YAML configuration for providing rules and users can maintain the file in the repository and provide the path in the SE configuration, rules_df has to be built by default.
Describe the solution you'd like
Add new argument while instantiating
with_expectationsto providerules_yaml_pathorrules_df{}Describe alternatives you've considered{} We had rules_table earlier which we removed as it is not generic. Having a YAML in the repository would be a generic native solution, but users will still have autonomy on bringing their own rules_df if needed. This should be a new plugin that takes in different file formats. We want to standardize it to YAML, but it should have flexibility to extend to json etc.