Adding deprecation warning really screws up any existing scripts

[SteveH-US]

trafficstars

Describe the bug A clear and concise description of the bug. The new version of the mongocli, v1.24.1 adds the following message "⚠ There's a new, dedicated Atlas CLI available for Atlas users. Install the Atlas CLI to enjoy the same capabilities and keep getting new features: https://dochub.mongodb.org/core/migrate-to-atlas-cli. Atlas commands for MongoCLI are now deprecated, but you can keep using them for 12 months (until April 30, 2023)."

That really screws up any reports that use this CLI today. There is a less invasive way to tell us than to print out this warning to stderr, which is its an odd way to use stderr.

To Reproduce Steps to reproduce the behavior:

1. Run '...'
2. See error

Expected behavior Please explain what you expected to happen.

Please remove this output.

Screenshots If possible, add screenshots to help explain your problem.

Desktop (please complete the following information):

• OS: [e.g. Ubuntu Linux 18.04]
• MongoCLI version [e.g. 1.2]
• Ops Manager Version: [if applicable]

Additional context Add any other context about the problem here.

[boooczek]

@SteveH-US thank you for pointing our attention to this issue. In your opinion, what would be the expected way to notify about this deprecation?

[github-actions[bot]]

This issue has gone 30 days without any activity and meets the project’s definition of "stale". This will be auto-closed if there is no new activity over the next 30 days. If the issue is still relevant and active, you can simply comment with a "bump" to keep it open, or add the label "not_stale". Thanks for keeping our repository healthy!

[SteveH-US]

I think it's sufficient to list that the command is deprecated in the help and not send noise to standard error.

[github-actions[bot]]

This issue has gone 30 days without any activity and meets the project’s definition of "stale". This will be auto-closed if there is no new activity over the next 30 days. If the issue is still relevant and active, you can simply comment with a "bump" to keep it open, or add the label "not_stale". Thanks for keeping our repository healthy!

[SteveH-US]

bump

[boooczek]

@SteveH-US I'm sorry for the late response here and thank you for your previous answer. I'm also very sorry this change had such impact on your work. We believe that displaying the message in help will not provide enough visibility to users. Because of that we've decided to surface it as stderr. In order to avoid this change breaking your reports, we recommend piping the stderr to a different file.

In meantime, what're your plans of migrating to the Atlas CLI?

[SteveH-US]

I have already migrated to the atlas CLI. I had to quickly because of this problem.

[github-actions[bot]]

This issue has gone 30 days without any activity and meets the project’s definition of "stale". This will be auto-closed if there is no new activity over the next 30 days. If the issue is still relevant and active, you can simply comment with a "bump" to keep it open, or add the label "not_stale". Thanks for keeping our repository healthy!