Currently the validate_bundle() and get_config_bundle() methods do a deepcopy of the result before returning it. This was necessary back when the config source was itself mutated and so needed to be copied. Now that the source and validated config are separate copies anyway, having the bundles return as references rather than copies would be convenient to allow systems to mutate their own configuration, while still maintaining the ability to have a "source of truth" by calling validate_bundle().
Currently the `validate_bundle()` and `get_config_bundle()` methods do a deepcopy of the result before returning it. This was necessary back when the config source was itself mutated and so needed to be copied. Now that the source and validated config are separate copies anyway, having the bundles return as references rather than copies would be convenient to allow systems to mutate their own configuration, while still maintaining the ability to have a "source of truth" by calling `validate_bundle()`.
Currently the
validate_bundle()andget_config_bundle()methods do a deepcopy of the result before returning it. This was necessary back when the config source was itself mutated and so needed to be copied. Now that the source and validated config are separate copies anyway, having the bundles return as references rather than copies would be convenient to allow systems to mutate their own configuration, while still maintaining the ability to have a "source of truth" by callingvalidate_bundle().Looks like
get_config_bundle()was already doing this anyway 😕