Closed j2ein closed 1 month ago
I don't think these are "errors". The log messages afterwards also indicate that "registering new bee" if no config is found. This is why those messages were written inside log.WithField.Infof()
, not log.WithField.Errorf()
.
I will close this issue, but feel free to re-open if anyone disagrees with this decision.
Is your feature request related to a problem? Please describe. The first startup of a bee has error messages despite the startup being successful, e.g. no config found, no destination beehive found. This confuses users that choose to look at the logs.
Describe the solution you'd like These errors should be prevented, when the startup is actually successful.
Describe alternatives you've considered
Additional context