-
Notifications
You must be signed in to change notification settings - Fork 2.7k
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
Kubernetes: remove useless and potentially confusing dekorate output #8798
Comments
I agree this should be debug. @geoand WDYT? |
Yeah, this output make no sense most of the time and should be debug logging |
@metacosm do you plan on working on this? It looks like it might need some changed in dekorate as well, since these messages come from an internal dekorate implementation (which I assume was done to get past problems with logging and annotation processors). |
Planning on working on #8792 first, though I might work on this at the same time. |
Cool |
I'll do this one real quick then :) |
This also requires: dekorateio/dekorate#488 I should have fixed that in the first place... Oh well |
I removed the backport tag and marked it for 1.5.0 so that we don't forget about it. |
Good idea. This needs a new dekorate release to be properly fixed |
Description
When using the Kubernetes extension, one will see the following (or similar output) during build:
This not only doesn't provide any useful information but is potentially confusing, in particular when neither openshift nor s2i extensions are enabled.
The text was updated successfully, but these errors were encountered: