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

Provider cleanup (safe part) #726

Merged
merged 6 commits into from
Apr 3, 2024

Conversation

stevenpost
Copy link
Contributor

This PR cleans up the provider.

A detailed list of changes:

  • Drop support for obsolete file locations
  • Drop old work-arounds
  • Simplify authentication logic in mongoshrc.js (making it a bit less error-prone)
  • Refactor out code for pre-2.6 config

Since we are in the `else` clause and `port` already evaluates to false,
we can be pretty confident on how `!port` will evaluate.
This was put in place for the `mongo` command in the provider. But we
now use a different provider.
No need to switch between databases.
@stevenpost stevenpost mentioned this pull request Apr 2, 2024
The boolean check was there for old config. See commits
1bb1995
6cd09d1
@stevenpost stevenpost changed the title Provider cleanup Provider cleanup (safe part) Apr 2, 2024
@stevenpost stevenpost marked this pull request as ready for review April 2, 2024 15:57
@witjoh witjoh merged commit ba8fb13 into voxpupuli:master Apr 3, 2024
24 checks passed
@stevenpost stevenpost deleted the provider_cleanup_safe branch April 3, 2024 08:45
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.

3 participants