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

Don't let provider depend on client files #717

Open
stevenpost opened this issue Mar 24, 2024 · 2 comments
Open

Don't let provider depend on client files #717

stevenpost opened this issue Mar 24, 2024 · 2 comments

Comments

@stevenpost
Copy link
Contributor

We don't have to do anything about this now, as it's the same with mongorc.
But IMO users should be able to manage this file however they like without breaking the provider.

Originally posted by @h-haaks in #703 (comment)

@stevenpost
Copy link
Contributor Author

A possible solution would be to put credentials as parameters in the call to mongosh. However that approach is vulnerable to ps sniping, although that is solvable by doing some input redirection from a file Another possible solution would be the use of certificated for authentication..

@stevenpost
Copy link
Contributor Author

Some additional info.

This file exists solely to make life easier for developing the provider, it basically serves 2 purposes:

  • Add conditional logic for authentication
  • Add 2 functions to help in replicaset management

IMHO, the functions need to be moved inline with the provider and there needs to be a solution to the authentication. Changing this file now restarts the server, which is utter nonsense. To be clear, currently, changing the admin password causes a server restart.

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

No branches or pull requests

1 participant