mirror of
https://github.com/grafana/grafana.git
synced 2025-09-25 18:44:10 +08:00
Chore: typos in MySQL/PostgreSQL ConfigurationEditor (#52735)
This commit is contained in:
@ -169,8 +169,8 @@ export const ConfigurationEditor = (props: DataSourcePluginOptionsEditorProps<My
|
|||||||
The database user should only be granted SELECT permissions on the specified database & tables you want to
|
The database user should only be granted SELECT permissions on the specified database & tables you want to
|
||||||
query. Grafana does not validate that queries are safe so queries can contain any SQL statement. For example,
|
query. Grafana does not validate that queries are safe so queries can contain any SQL statement. For example,
|
||||||
statements like <code>USE otherdb;</code> and <code>DROP TABLE user;</code> would be executed. To protect
|
statements like <code>USE otherdb;</code> and <code>DROP TABLE user;</code> would be executed. To protect
|
||||||
against this we
|
against this we <strong>Highly</strong> recommend you create a specific MySQL user with restricted permissions.
|
||||||
<strong>Highly</strong> recommmend you create a specific MySQL user with restricted permissions. Checkout the{' '}
|
Checkout the{' '}
|
||||||
<Link rel="noreferrer" target="_blank" href="http://docs.grafana.org/features/datasources/mysql/">
|
<Link rel="noreferrer" target="_blank" href="http://docs.grafana.org/features/datasources/mysql/">
|
||||||
MySQL Data Source Docs
|
MySQL Data Source Docs
|
||||||
</Link>
|
</Link>
|
||||||
|
@ -273,8 +273,8 @@ export const PostgresConfigEditor = (props: DataSourcePluginOptionsEditorProps<P
|
|||||||
The database user should only be granted SELECT permissions on the specified database & tables you want to
|
The database user should only be granted SELECT permissions on the specified database & tables you want to
|
||||||
query. Grafana does not validate that queries are safe so queries can contain any SQL statement. For example,
|
query. Grafana does not validate that queries are safe so queries can contain any SQL statement. For example,
|
||||||
statements like <code>DELETE FROM user;</code> and <code>DROP TABLE user;</code> would be executed. To protect
|
statements like <code>DELETE FROM user;</code> and <code>DROP TABLE user;</code> would be executed. To protect
|
||||||
against this we
|
against this we <strong>Highly</strong> recommend you create a specific PostgreSQL user with restricted
|
||||||
<strong>Highly</strong> recommmend you create a specific PostgreSQL user with restricted permissions.
|
permissions.
|
||||||
</Alert>
|
</Alert>
|
||||||
</>
|
</>
|
||||||
);
|
);
|
||||||
|
Reference in New Issue
Block a user