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

Add strong warning against production use to example init_db.sql file #4815

Merged
merged 2 commits into from
Apr 17, 2019

Conversation

teejae
Copy link
Contributor

@teejae teejae commented Apr 17, 2019

Signed-off-by: Toliver Jue toliver@planetscale.com

Signed-off-by: Toliver Jue <toliver@planetscale.com>
@teejae teejae requested a review from sougou as a code owner April 17, 2019 01:51
###############################################################################
# WARNING: This sql is *NOT* safe for production use,
# as it contains default users and passwords
# with more privileges than necessary.
Copy link
Member

Choose a reason for hiding this comment

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

As far as I know, the privileges given are necessary. Is there an example you see that's unnecessary?

The main thing that we intended for people to change but didn't document well enough is the passwords, especially for the users that allow remote connections.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

I've removed comment about privileges, and added comment about rotating them as necessary.

Copy link
Member

@enisoc enisoc left a comment

Choose a reason for hiding this comment

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

lgtm

@enisoc enisoc merged commit 7329452 into vitessio:master Apr 17, 2019
@enisoc enisoc deleted the tj-add-init-db-warning branch April 17, 2019 05:12
@deepthi
Copy link
Member

deepthi commented Apr 17, 2019 via email

@enisoc
Copy link
Member

enisoc commented Apr 17, 2019

The single, squashed commit seems to have the DCO: 7329452

@deepthi
Copy link
Member

deepthi commented Apr 17, 2019

I see that now. This is confusing because github is still showing 2 commits on the PR, but looks like we should be fine.

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