Sergey Vasilyev
Sergey Vasilyev
It is not about Kopf, it is about running a generic Python app and is (or is not) an issue of Python. Afair, this was the default behavor for years,...
CLI already allows this, basically in any shell: ``` PYTHONPATH=. kopf run -m some.module PYTHONPATH=/home/…/dir1:/opt/myoperator/dir2 kopf run -m some.module ``` Not specific to Kopf, this is a Python feature: *...
Hello. Sorry for the late response — I somehow missed the notification email. Can you please clarify what do you mean by "anywhere else"? The solution intentionally bans "anywhere else"...
Sorry, there is no sufficient information to debug the issue. It does not happen to me. If you find the cause and make a fix, please send a PR. What...
Hi. Thanks for reporting the issue. Can you please provide a repro with the setup that leads to this error?
Thanks. (I meant repro, not repo — something to reproduce the issue. Sorry for this.) As for the issue: it is difficult to say without a deep dive into the...
Hello. I don’t know. You can try.
At least, the next major/minor/micro/rc/dev version should be calculated and printed to stdout. Some CI/CD tools do not have the permissions to push to the git repos from the build...
This bug —if it is a bug— is too specific to a particular third-party operator (ArgoCD in this case). I am not sure if Kopf has anything to do with...
This issue is similar to #62 regarding inconsistencies of the parsed outcome, but there is a different outcome structure is suggested, which also contains meta-information on the original config (attrs...