```bash helm install --set existingSecret=my-minio-secret minio/minio ``` The following fields are expected in the secret: | .data.\<key\> in Secret | Corresponding variable | Description | Required | |:-------- | `rootUser` | `rootUser` | Root user. | yes | | `rootPassword` | `rootPassword` | Root password. | yes | All corresponding variables will be ignored in values file. ### Configure TLS To enable TLS for MinIO containers, acquire TLS certificates from a CA or create self-signed certificates. While...

- limit the number of active requests allowed across the cluster
- limit the wait duration for each request in the queue

These values are enabled using server's configuration or environment variables.

## Examples

### Configuring connection limit

  - Retention headers can be optionally set while uploading objects
  - Once objects are uploaded PutObjectRetention API can be called to change retention settings
- *MINIO_NTP_SERVER* environment variable can be set to remote NTP server endpoint if system time is not desired for setting retention dates.

## Explore Further

```bash helm install --set existingSecret=my-minio-secret minio/minio ``` The following fields are expected in the secret: | .data.<key> in Secret | Corresponding variable | Description | Required | |:-------- | `rootUser` | `rootUser` | Root user. | yes | | `rootPassword` | `rootPassword` | Root password. | yes | All corresponding variables will be ignored in values file. Configure TLS ---------- To enable TLS for MinIO containers, acquire TLS certificates from a CA or create self-signed certificates....

```bash helm install --set existingSecret=my-minio-secret minio/minio ``` The following fields are expected in the secret: | .data.<key> in Secret | Corresponding variable | Description | Required | |:-------- | `rootUser` | `rootUser` | Root user. | yes | | `rootPassword` | `rootPassword` | Root password. | yes | All corresponding variables will be ignored in values file. Configure TLS ---------- To enable TLS for MinIO containers, acquire TLS certificates from a CA or create self-signed certificates....

```bash helm install --set existingSecret=my-minio-secret minio/minio ``` The following fields are expected in the secret: | .data.<key> in Secret | Corresponding variable | Description | Required | |:-------- | `rootUser` | `rootUser` | Root user. | yes | | `rootPassword` | `rootPassword` | Root password. | yes | All corresponding variables will be ignored in values file. Configure TLS ---------- To enable TLS for MinIO containers, acquire TLS certificates from a CA or create self-signed certificates....

```bash helm install --set existingSecret=my-minio-secret minio/minio ``` The following fields are expected in the secret: | .data.<key> in Secret | Corresponding variable | Description | Required | |:-------- | `rootUser` | `rootUser` | Root user. | yes | | `rootPassword` | `rootPassword` | Root password. | yes | All corresponding variables will be ignored in values file. Configure TLS ---------- To enable TLS for MinIO containers, acquire TLS certificates from a CA or create self-signed certificates....

Imagina que quieres que el parámetro sea `item-query`.

Como en:

```
http://127.0.0.1:8000/items/?item-query=foobaritems
```

Pero `item-query` no es un nombre de variable válido en Python.

Lo más cercano sería `item_query`.

Pero aún necesitas que sea exactamente `item-query`...

Entonces puedes declarar un `alias`, y ese alias será usado para encontrar el valor del parámetro:

// sufficient to initialize a [Buffer].
func NewBuffer(buf []byte) *Buffer { return &Buffer{buf: buf} }

// NewBufferString creates and initializes a new [Buffer] using string s as its
// initial contents. It is intended to prepare a buffer to read an existing
// string.
//
// In most cases, new([Buffer]) (or just declaring a [Buffer] variable) is
// sufficient to initialize a [Buffer].

  }

  /*
   * To avoid the need to call requireNonNull so much, we could consider more clever approaches,
   * such as:
   *
   * - Make checkOpen return the non-null `seq`. Then callers can assign that to a local variable or
   *   even back to `this.seq`. However, that may suggest that we're defending against concurrent
   *   mutation, which is not an actual risk because we use `synchronized`.