Clarify security configuration request

This commit is contained in:
aetter 2021-05-17 08:49:26 -07:00
parent 534bd82454
commit d86ba8e5fc
1 changed files with 2 additions and 2 deletions

View File

@ -1030,7 +1030,7 @@ GET _opensearch/_security/api/securityconfig
### Update configuration
Creates or updates the existing configuration using the REST API rather than `securityadmin.sh`. This operation can easily break your existing configuration, so we recommend using `securityadmin.sh` instead. See [Access control for the API](#access-control-for-the-api) for how to enable this operation.
Creates or updates the existing configuration using the REST API. This operation can easily break your existing configuration, so we recommend using `securityadmin.sh` instead, which is far safer. See [Access control for the API](#access-control-for-the-api) for how to enable this operation.
#### Request
@ -1088,7 +1088,7 @@ PUT _opensearch/_security/api/securityconfig/config
### Patch configuration
Updates the existing configuration using the REST API rather than `securityadmin.sh`. This operation can easily break your existing configuration, so we recommend using `securityadmin.sh` instead. See [Access control for the API](#access-control-for-the-api) for how to enable this operation.
Updates the existing configuration using the REST API. This operation can easily break your existing configuration, so we recommend using `securityadmin.sh` instead, which is far safer. See [Access control for the API](#access-control-for-the-api) for how to enable this operation.
#### Request