Enhance MCAD Logs and fix naming consistency #645
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Issue link
Resolves #644
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.
Previously:
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.What changes have been made
namespace/name
.Verification steps
<namespace/name>
of your AW.Checks