Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[226] Use patch instead of update to change pod labels #227

Merged
merged 2 commits into from
Jun 20, 2022

Conversation

yersan
Copy link
Collaborator

@yersan yersan commented Jun 17, 2022

fixes #226

return err
}

logger.Info("Patched resource")
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@yersan should this be logged at Debug level?

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Good point, it can be a debug level instead, I just followed the same pattern we had for the other actions, but it is very verbose indeed.

Copy link
Collaborator Author

@yersan yersan Jun 17, 2022

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@jmesnil I've changed the message to debug level for the trace that confirms the action taken. There is no need to show it as info, if the operation fails an error is logged, otherwise, we can assume it was executed successfully, no need to log such a confirmation

…te/read/update/pacth/delete) taken on a resource
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

OCP 4.11 with WildFly operator can not scale down to 0
2 participants