You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This happens because process.check is used which logs the remote command at info level. The workaround is to set the level higher, but this would cause other useful information to be omitted.
The function docstring is logging at debug level for example. Not a good combination, and this output is overkill:
INFO:ADEZA:Running command: kubectl get pod -l component=api -n current -o name
DEBUG:ADEZA:trying to determine remote python executable with python3
INFO:ADEZA:Running command: kubectl exec -i -n current pod/current-anchore-engine-api-554689b88d-khhhv -- /bin/sh -c which python3
INFO:ADEZA:Running command: kubectl exec -i -n current pod/current-anchore-engine-api-554689b88d-khhhv -- /bin/sh -c /usr/bin/python3
INFO:ADEZA:Running command: kubectl exec -i -n current pod/current-anchore-engine-api-554689b88d-khhhv -- /bin/sh -c /usr/bin/python3
INFO:ADEZA:Running command: kubectl exec -i -n current pod/current-anchore-engine-api-554689b88d-khhhv -- /bin/sh -c /usr/bin/python3
INFO:ADEZA:Running command: kubectl exec -i -n current pod/current-anchore-engine-api-554689b88d-khhhv -- /bin/sh -c /usr/bin/python3
INFO:ADEZA:Running command: kubectl exec -i -n current pod/current-anchore-engine-api-554689b88d-khhhv -- /bin/sh -c /usr/bin/python3
INFO:ADEZA:Running command: kubectl exec -i -n current pod/current-anchore-engine-api-554689b88d-khhhv -- /bin/sh -c /usr/bin/python3
INFO:ADEZA:Running command: kubectl exec -i -n current pod/current-anchore-engine-api-554689b88d-khhhv -- /bin/sh -c /usr/bin/python3
INFO:ADEZA:Running command: kubectl exec -i -n current pod/current-anchore-engine-api-554689b88d-khhhv -- /bin/sh -c /usr/bin/python3
INFO:ADEZA:Running command: kubectl exec -i -n current pod/current-anchore-engine-api-554689b88d-khhhv -- /bin/sh -c /usr/bin/python3
INFO:ADEZA:Running command: kubectl exec -i -n current pod/current-anchore-engine-api-554689b88d-khhhv -- /bin/sh -c /usr/bin/python3
INFO:ADEZA:Running command: kubectl exec -i -n current pod/current-anchore-engine-api-554689b88d-khhhv -- /bin/sh -c /usr/bin/python3
INFO:ADEZA:Running command: kubectl exec -i -n current pod/current-anchore-engine-api-554689b88d-khhhv -- /bin/sh -c /usr/bin/python3
INFO:ADEZA:Running command: kubectl exec -i -n current pod/current-anchore-engine-api-554689b88d-khhhv -- /bin/sh -c /usr/bin/python3
INFO:ADEZA:Running command: kubectl exec -i -n current pod/current-anchore-engine-api-554689b88d-khhhv -- /bin/sh -c /usr/bin/python3
INFO:ADEZA:Running command: kubectl exec -i -n current pod/current-anchore-engine-api-554689b88d-khhhv -- /bin/sh -c /usr/bin/python3
INFO:ADEZA:Running command: kubectl exec -i -n current pod/current-anchore-engine-api-554689b88d-khhhv -- /bin/sh -c /usr/bin/python3
INFO:ADEZA:Running command: kubectl exec -i -n current pod/current-anchore-engine-api-554689b88d-khhhv -- /bin/sh -c /usr/bin/python3
INFO:ADEZA:Running command: kubectl exec -i -n current pod/current-anchore-engine-api-554689b88d-khhhv -- /bin/sh -c /usr/bin/python3
INFO:ADEZA:Running command: kubectl exec -i -n current pod/current-anchore-engine-api-554689b88d-khhhv -- /bin/sh -c /usr/bin/python3
INFO:ADEZA:Running command: kubectl exec -i -n current pod/current-anchore-engine-api-554689b88d-khhhv -- /bin/sh -c /usr/bin/python3
INFO:ADEZA:Running command: kubectl exec -i -n current pod/current-anchore-engine-api-554689b88d-khhhv -- /bin/sh -c /usr/bin/python3
The text was updated successfully, but these errors were encountered:
This happens because
process.check
is used which logs the remote command atinfo
level. The workaround is to set the level higher, but this would cause other useful information to be omitted.The function docstring is logging at
debug
level for example. Not a good combination, and this output is overkill:The text was updated successfully, but these errors were encountered: