It's simple, the logs when loading it via a module don't give you enough information about the module which the function is called from, for example, we frequently call the 'create' function as create and so looking over the logs, we can't tell which operator was the one that did the create.
Proposal
It would be nice if we had a prefixed path, something like:
openstack_operator.memcached.create
Or something along those lines.
Checklist
[X] Many users can benefit from this feature, it is not a one-time case
[X] The proposal is related to the K8s operator framework, not to the K8s client libraries
First of all, excellent work on the operator, we're moving away from kubebuilder and adopting it here:
https://opendev.org/vexxhost/openstack-operator
Slowly but surely, the codebase is shaping up. :)
Problem
It's simple, the logs when loading it via a module don't give you enough information about the module which the function is called from, for example, we frequently call the 'create' function as
createand so looking over the logs, we can't tell which operator was the one that did thecreate.Proposal
It would be nice if we had a prefixed path, something like:
Or something along those lines.
Checklist