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
There are several instances where the logs provide inconsistent naming on the AppWrapper or Job:
There are a number of instances where the logs only provide the name of the AppWrapper or Job, instead of following the most used pattern of namespace/name as done i.e., here.
There are a couple of places where the logs display name/name, such as here.
A few places have the name/namespace pattern, which can be inconsistent when looking/searching through the logs.
Few instances where i.e., qj.Name is provided in the Info log but not used.
Expected Behavior
We want the logs to be consistent throughout the repo for better readability, troubleshooting, and accuracy.
Motivation
In the scenario where we want to create an AW in two different namespaces but with the same name, it is important to know which AppWrapper the logs are referring to.
The text was updated successfully, but these errors were encountered:
Logs Enhancement
There are several instances where the logs provide inconsistent naming on the AppWrapper or Job:
There are a number of instances where the logs only provide the
name
of the AppWrapper or Job, instead of following the most used pattern ofnamespace/name
as done i.e., here.There are a couple of places where the logs display
name/name
, such as here.A few places have the
name/namespace
pattern, which can be inconsistent when looking/searching through the logs.Few instances where i.e.,
qj.Name
is provided in the Info log but not used.Expected Behavior
We want the logs to be consistent throughout the repo for better readability, troubleshooting, and accuracy.
Motivation
In the scenario where we want to create an AW in two different namespaces but with the same name, it is important to know which AppWrapper the logs are referring to.
The text was updated successfully, but these errors were encountered: