Module Contents



Anonymize string names in an optionally-consistent way.

class great_expectations.core.usage_statistics.anonymizers.checkpoint_run_anonymizer.CheckpointRunAnonymizer(salt=None)

Bases: great_expectations.core.usage_statistics.anonymizers.anonymizer.Anonymizer

Anonymize string names in an optionally-consistent way.

anonymize_checkpoint_run(self, *args, **kwargs)

Traverse the entire Checkpoint configuration structure (as per its formal, validated Marshmallow schema) and anonymize every field that can be customized by a user (public fields are recorded as their original names).

static resolve_config_using_acceptable_arguments(checkpoint: Checkpoint, template_name: Optional[str] = None, run_name_template: Optional[str] = None, expectation_suite_name: Optional[str] = None, batch_request: Optional[Union[BatchRequest, RuntimeBatchRequest, dict]] = None, action_list: Optional[List[dict]] = None, evaluation_parameters: Optional[dict] = None, runtime_configuration: Optional[dict] = None, validations: Optional[List[dict]] = None, profilers: Optional[List[dict]] = None, run_id: Optional[Union[str, RunIdentifier]] = None, run_name: Optional[str] = None, run_time: Optional[Union[str, datetime.datetime]] = None, result_format: Optional[Union[str, dict]] = None, expectation_suite_ge_cloud_id: Optional[str] = None)

This method reconciles the Checkpoint configuration (e.g., obtained from the Checkpoint store) with dynamically supplied arguments in order to obtain that Checkpoint specification that is ready for running validation on it. This procedure is necessecitated by the fact that the Checkpoint configuration is hierarchical in its form, which was established for the purposes of making the specification of different Checkpoint capabilities easy. In particular, entities, such as BatchRequest, expectation_suite_name, and action_list, can be specified at the top Checkpoint level with the suitable ovverrides provided at lower levels (e.g., in the validations section). Reconciling and normalizing the Checkpoint configuration is essential for usage statistics, because the exact values of the entities in their formally validated form (e.g., BatchRequest) is the required level of detail.