Add container name to new image found log, useful when running monitor-only #1870
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.
What your PR contributes
Simply added the container name to the "Found new image" log, because in monitor-only it's not clear which container needs to be recreated, also there are duplicate log lines if the same image is used in multiple containers (MariaDB etc). I added it to the end of the message to limit issues if people are parsing the log message in their workflows.
Which issues it solves
No issue, I can open one if required but for such a tiny change I thought any discussion could happen here.
Tests that verify the code your contributing
Unable to get a dev env set up, there are no instructions on the project. Unable to build a test docker image that runs. The Go compiler doesn't complain though, which from such a small change I would expect it to if I'd gone wrong.
Updates to the documentation
None required