Update changelog

Signed-off-by: dependabot[bot] <support@github.com>

Author: dependabot[bot]

CHANGELOG.md

@@ -161,7 +161,8 @@ Inspired from [Keep a Changelog](https://keepachangelog.com/en/1.0.0/)
 ### Security
 
 ### Dependencies
-
+- Bump `github.com/aws/aws-sdk-go-v2/config` from 1.32.6 to 1.32.7 ([#767](https://github.com/opensearch-project/opensearch-go/pull/767))
+- Bump `github.com/aws/aws-sdk-go-v2/credentials` from 1.19.7 to 1.19.12 ([#807](https://github.com/opensearch-project/opensearch-go/pull/807))
 - Bump `github.com/aws/aws-sdk-go-v2/config` from 1.32.6 to 1.32.7 ([#767](https://github.com/opensearch-project/opensearch-go/pull/767))
 
 ## [4.6.0]

guides/cluster_health_checking.md

@@ -80,10 +80,10 @@ The capacity model values (`clientsPerServer`, `healthCheckRate`) are auto-deriv
 
 ### Configuration
 
-| Config Field                 | Default | Description                                                                                                                   |
-| ---------------------------- | ------- | ----------------------------------------------------------------------------------------------------------------------------- |
-| `MaxRetryClusterHealth`      | `4h`    | Retry interval for re-probing unavailable nodes. `0` = use default, `<0` = disable probing entirely.                          |
-| `HealthCheckRequestModifier` | `nil`   | Callback applied to every health check request (both `GET /` and `/_cluster/health`). Use this to inject custom auth headers. |
+| Config Field | Default | Description |
+| --- | --- | --- |
+| `MaxRetryClusterHealth` | `4h` | Retry interval for re-probing unavailable nodes. `0` = use default, `<0` = disable probing entirely. |
+| `HealthCheckRequestModifier` | `nil` | Callback applied to every health check request (both `GET /` and `/_cluster/health`). Use this to inject custom auth headers. |
 
 ```go
 client, err := opensearchapi.NewClient(opensearchapi.Config{
@@ -130,11 +130,11 @@ The response is a JSON object:
 
 The `status` field reports overall cluster health:
 
-| Status   | Meaning                                                                                                        |
-| -------- | -------------------------------------------------------------------------------------------------------------- |
-| `green`  | All primary and replica shards are assigned.                                                                   |
+| Status | Meaning |
+| --- | --- |
+| `green` | All primary and replica shards are assigned. |
 | `yellow` | All primary shards are assigned, but some replicas are not. The cluster is functional but not fully redundant. |
-| `red`    | Some primary shards are unassigned. Data loss or unavailability may be occurring.                              |
+| `red` | Some primary shards are unassigned. Data loss or unavailability may be occurring. |
 
 A single-node development cluster will always report `yellow` because there is no second node to host replica shards. This is expected and does not indicate a problem.
 
@@ -150,16 +150,16 @@ The client uses poll-and-parse instead: issue the request, read the `status` fie
 
 ## HTTP Response Status Codes
 
-| HTTP Status | Meaning                                                                             |
-| ----------- | ----------------------------------------------------------------------------------- |
-| **200**     | Success. Parse the `status` and `timed_out` fields from the response body.          |
-| **400**     | Malformed request (invalid query parameters).                                       |
-| **401**     | Authentication failure: credentials are missing or invalid.                         |
-| **403**     | Authorization failure: the user is authenticated but lacks the required permission. |
-| **408**     | The request timed out. Only occurs when `wait_for_*` parameters are used.           |
-| **429**     | The node's thread pool rejected the request (server-side backpressure).             |
-| **500**     | Unexpected server error.                                                            |
-| **503**     | The node is not ready to accept requests (e.g., still starting up).                 |
+| HTTP Status | Meaning |
+| --- | --- |
+| **200** | Success. Parse the `status` and `timed_out` fields from the response body. |
+| **400** | Malformed request (invalid query parameters). |
+| **401** | Authentication failure: credentials are missing or invalid. |
+| **403** | Authorization failure: the user is authenticated but lacks the required permission. |
+| **408** | The request timed out. Only occurs when `wait_for_*` parameters are used. |
+| **429** | The node's thread pool rejected the request (server-side backpressure). |
+| **500** | Unexpected server error. |
+| **503** | The node is not ready to accept requests (e.g., still starting up). |
 
 ### Distinguishing Auth Errors from Cluster Failures
 
@@ -265,21 +265,21 @@ PUT /_plugins/_security/api/rolesmapping/health_check
 
 Before creating a custom role, check whether an existing role already provides sufficient access:
 
-| Role                           | Permissions                                         | Notes                                                                                               |
-| ------------------------------ | --------------------------------------------------- | --------------------------------------------------------------------------------------------------- |
-| `cluster_monitor`              | `cluster:monitor/*`                                 | Covers health, stats, and all monitoring endpoints. Broader than necessary for health checks alone. |
-| `opensearch_dashboards_server` | Includes cluster monitoring among other privileges. | Intended for the Dashboards service account.                                                        |
+| Role | Permissions | Notes |
+| --- | --- | --- |
+| `cluster_monitor` | `cluster:monitor/*` | Covers health, stats, and all monitoring endpoints. Broader than necessary for health checks alone. |
+| `opensearch_dashboards_server` | Includes cluster monitoring among other privileges. | Intended for the Dashboards service account. |
 
 The minimal custom `health_check` role with only `cluster:monitor/health` follows the principle of least privilege.
 
 ## Transitioning from an Unsecured Cluster
 
 When a cluster transitions from no security (Security plugin disabled) to security enabled, the behavior changes:
 
-| Before security                           | After security                                                                                 |
-| ----------------------------------------- | ---------------------------------------------------------------------------------------------- |
-| All requests succeed with no credentials. | Requests without valid credentials return **401**.                                             |
-| No permission checks.                     | Requests with valid credentials but missing `cluster:monitor/health` privilege return **403**. |
+| Before security | After security |
+| --- | --- |
+| All requests succeed with no credentials. | Requests without valid credentials return **401**. |
+| No permission checks. | Requests with valid credentials but missing `cluster:monitor/health` privilege return **403**. |
 
 If the client is performing health checks and the cluster enables security, health probes will begin returning 401. This is expected. The client should surface this condition clearly rather than reporting the cluster as unhealthy: the cluster is reachable, but credentials need to be configured.
 

guides/error_handling.md

@@ -22,13 +22,13 @@ This design maximizes availability but requires careful error checking in client
 
 ### Operations That Can Have Partial Failures
 
-| Operation               | HTTP Status | Partial Failure Indicator | Impact                                    |
-| ----------------------- | ----------- | ------------------------- | ----------------------------------------- |
-| **Bulk**                | 200         | `errors: true`            | Data loss - some documents not indexed    |
-| **Search**              | 200         | `_shards.failed > 0`      | Incomplete results - missing data         |
-| **Index/Update/Delete** | 201/200     | `_shards.failed > 0`      | Durability risk - no replica confirmation |
-| **Refresh**             | 200         | `_shards.failed > 0`      | Incomplete refresh                        |
-| **Cluster operations**  | 200         | `_shards.failed > 0`      | Incomplete stats/operations               |
+| Operation | HTTP Status | Partial Failure Indicator | Impact |
+| --- | --- | --- | --- |
+| **Bulk** | 200 | `errors: true` | Data loss - some documents not indexed |
+| **Search** | 200 | `_shards.failed > 0` | Incomplete results - missing data |
+| **Index/Update/Delete** | 201/200 | `_shards.failed > 0` | Durability risk - no replica confirmation |
+| **Refresh** | 200 | `_shards.failed > 0` | Incomplete refresh |
+| **Cluster operations** | 200 | `_shards.failed > 0` | Incomplete stats/operations |
 
 ## Checking for Partial Failures
 
@@ -341,23 +341,23 @@ func (m *OperationMetrics) Report() {
 
 ### Bulk Operation Errors
 
-| Error Type                          | Description                        | Retryable? | Action                                                                  |
-| ----------------------------------- | ---------------------------------- | ---------- | ----------------------------------------------------------------------- |
-| `mapper_parsing_exception`          | Invalid document format            | No         | Fix document                                                            |
-| `version_conflict_engine_exception` | Version conflict                   | Maybe      | Retry with updated version                                              |
-| `document_missing_exception`        | Document not found (update/delete) | No         | Skip or create                                                          |
-| `es_rejected_execution_exception`   | Queue full                         | Yes        | Retry with backoff                                                      |
-| `circuit_breaking_exception`        | Circuit breaker tripped            | Yes        | Retry with backoff                                                      |
-| `timeout_exception`                 | Operation timeout                  | Yes        | Retry; see [Bulk: Timeout Configuration](bulk.md#timeout-configuration) |
+| Error Type | Description | Retryable? | Action |
+| --- | --- | --- | --- |
+| `mapper_parsing_exception` | Invalid document format | No | Fix document |
+| `version_conflict_engine_exception` | Version conflict | Maybe | Retry with updated version |
+| `document_missing_exception` | Document not found (update/delete) | No | Skip or create |
+| `es_rejected_execution_exception` | Queue full | Yes | Retry with backoff |
+| `circuit_breaking_exception` | Circuit breaker tripped | Yes | Retry with backoff |
+| `timeout_exception` | Operation timeout | Yes | Retry; see [Bulk: Timeout Configuration](bulk.md#timeout-configuration) |
 
 ### Shard Failure Reasons
 
-| Reason Type                        | Description           | Action               |
-| ---------------------------------- | --------------------- | -------------------- |
-| `shard_not_available_exception`    | Shard not ready       | Retry or wait        |
+| Reason Type | Description | Action |
+| --- | --- | --- |
+| `shard_not_available_exception` | Shard not ready | Retry or wait |
 | `primary_missing_action_exception` | Primary shard missing | Check cluster health |
-| `search_phase_execution_exception` | Search phase failed   | Review query         |
-| `illegal_argument_exception`       | Invalid parameters    | Fix query            |
+| `search_phase_execution_exception` | Search phase failed | Review query |
+| `illegal_argument_exception` | Invalid parameters | Fix query |
 
 ## Complete Example: Production-Ready Bulk Indexer
 

guides/node_discovery_and_roles.md

@@ -69,11 +69,11 @@ OpenSearch 3.0 introduced two significant role changes:
 
 These are distinct roles serving different purposes:
 
-| Role     | Purpose                   | Data Source                      | Write Traffic             |
-| -------- | ------------------------- | -------------------------------- | ------------------------- |
-| `search` | Dedicated search replicas | Replicated from primary shards   | None (read-only replicas) |
-| `warm`   | Searchable snapshots      | Snapshot storage (local/remote)  | None (read-only)          |
-| `data`   | General purpose           | Local shards (primary + replica) | Yes (indexing + search)   |
+| Role | Purpose | Data Source | Write Traffic |
+| --- | --- | --- | --- |
+| `search` | Dedicated search replicas | Replicated from primary shards | None (read-only replicas) |
+| `warm` | Searchable snapshots | Snapshot storage (local/remote) | None (read-only) |
+| `data` | General purpose | Local shards (primary + replica) | Yes (indexing + search) |
 
 ## Cluster Manager Filtering
 

guides/response_buffering.md

@@ -54,15 +54,15 @@ In both cases, always call `res.Body.Close()` when done.
 
 ## When to Use
 
-| Scenario                                           | Recommendation                    |
-| -------------------------------------------------- | --------------------------------- |
-| Standard API calls (CRUD, search, cluster ops)     | Leave buffering enabled (default) |
-| Reverse proxy forwarding large responses           | Disable buffering                 |
-| Streaming bulk responses to clients                | Disable buffering                 |
-| Scroll/PIT with large result sets piped downstream | Disable buffering                 |
+| Scenario | Recommendation |
+| --- | --- |
+| Standard API calls (CRUD, search, cluster ops) | Leave buffering enabled (default) |
+| Reverse proxy forwarding large responses | Disable buffering |
+| Streaming bulk responses to clients | Disable buffering |
+| Scroll/PIT with large result sets piped downstream | Disable buffering |
 
 ## Configuration Reference
 
-| Field                      | Type   | Default | Location                                          |
-| -------------------------- | ------ | ------- | ------------------------------------------------- |
+| Field | Type | Default | Location |
+| --- | --- | --- | --- |
 | `DisableResponseBuffering` | `bool` | `false` | `opensearch.Config`, `opensearchtransport.Config` |

guides/retry_backoff.md

@@ -66,10 +66,10 @@ To limit total wait time when the server is unresponsive, use a context with a d
 
 `RequestTimeout` and context deadlines serve different purposes:
 
-| Mechanism             | Scope       | Applies to                                                  |
-| --------------------- | ----------- | ----------------------------------------------------------- |
-| `RequestTimeout`      | Per-attempt | Each individual HTTP round-trip (including each retry)      |
-| `context.WithTimeout` | Total       | The entire operation across all attempts and backoff delays |
+| Mechanism | Scope | Applies to |
+| --- | --- | --- |
+| `RequestTimeout` | Per-attempt | Each individual HTTP round-trip (including each retry) |
+| `context.WithTimeout` | Total | The entire operation across all attempts and backoff delays |
 
 Use both together for defense in depth: `RequestTimeout` prevents any single attempt from hanging indefinitely, while a context deadline caps the total wall-clock time.