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

docker-machine: Deprecate both plugin and completion file #1779

Merged
merged 2 commits into from
Jan 29, 2021

Conversation

NoahGorny
Copy link
Member

@NoahGorny NoahGorny commented Jan 9, 2021

Closes #1744
Closes #1786

Description

Deprecate both plugin and completion file of docker-machine, as the command is deprecated as well.

Motivation and Context

See #1744 for context

How Has This Been Tested?

enabled locally, saw the error log

Types of changes

  • Bug fix (non-breaking change which fixes an issue)
  • New feature (non-breaking change which adds functionality)
  • Breaking change (fix or feature that would cause existing functionality to change)

Checklist:

  • My code follows the code style of this project.
  • If my change requires a change to the documentation, I have updated the documentation accordingly.
  • I have read the CONTRIBUTING document.
  • If I have added a new file, I also added it to clean_files.txt and formatted it using lint_clean_files.sh.
  • I have added tests to cover my changes, and all the new and existing tests pass.


complete -F _docker_machine docker-machine docker-machine.exe
# shellcheck shell=bash
_log_error '"docker-machine" is now deprecated, and as such the bash completion for it is also deprecated.
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Don't know if we discussed this before, but do we want to raise the deprecation as an error? Wouldn't a warning be sufficient?

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Hmm, I am unsure. I think errors are things that should be reported to us, while warning are warnings to the user, so I guess this really should just be log_warning. I say we merge this, and I will open an issue about it

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think we both agree that it should be a warning then?

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I updated the PR with a commit that changes all places like this

Noah Gorny added 2 commits January 29, 2021 16:06
Deprecated component is not an error, but instead should be a warning to
the user
@NoahGorny NoahGorny merged commit 293d867 into Bash-it:master Jan 29, 2021
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.

Logging warning and not error when deprecating component Deprecate Docker-Machine plugin and completion
3 participants