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

Remove "Clowder is not enabled" message #25

Merged
merged 1 commit into from
Oct 10, 2022

Conversation

lzap
Copy link
Contributor

@lzap lzap commented Sep 6, 2022

Hello, in our app, we use the same configuration for the backend app as well as for many CLI tools and this message is just always there. I see no big value in having anything on standard output, we use logging (and cloudwatch) anyways.

It's actually a really painful to use the common code in a config file generator which uses the standard output for the generated example configuration file. This dummy line is printed in init() which makes it impossible to avoid, once you import the package the message is there.

I'd appreciate a minor release with this so it goes away for good :-) Thanks a bunch, cheers!

Hello, in our app, we use the same configuration for the backend app as well as for many CLI tools and this message is just always there. I see no big value in having anything on standard output, we use logging (and cloudwatch) anyways.

I'd appreciate a minor release with this so it goes away for good :-) Thanks a bunch, cheers!
@psav psav merged commit 811f8bb into RedHatInsights:master Oct 10, 2022
@lzap lzap deleted the lzap-stdout-message branch October 10, 2022 08:43
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.

2 participants