Mas ainda é recomendado usar as ideias acima, usando várias classes, em vez desses parâmetros.

Isso ocorre porque o Schema JSON gerado no OpenAPI do seu aplicativo (e a documentação) ainda será o único para o modelo completo, mesmo que você use `response_model_include` ou `response_model_exclude` para omitir alguns atributos.

Isso também se aplica ao `response_model_by_alias` que funciona de forma semelhante.

///

```

### Accessing configuration

All configuration changes can be made using [`mc admin config` get/set/reset/export/import commands](https://github.com/minio/mc/blob/master/docs/minio-admin-complete-guide.md).

#### List all config keys available

```
~ mc admin config set myminio/
```

#### Obtain help for each key

```
~ mc admin config set myminio/ <key>
```

## Resumen

Con lo que has visto hasta ahora, puedes configurar una aplicación **FastAPI** segura usando estándares como OAuth2 y JWT.

En casi cualquier framework el manejo de la seguridad se convierte en un tema bastante complejo rápidamente.

        // This method should always return 0 as the request doesn't read responses
        assertEquals(0, bytesRead);
    }

    @Test
    @DisplayName("Test complete flow with all setters")
    void testCompleteFlow() {
        request = new Smb2SetInfoRequest(mockConfig);

        // Set all fields
        byte[] newFileId = new byte[16];
        for (int i = 0; i < 16; i++) {

            assertTrue(echoResponse.isSigned());
        }
    }

    @Nested
    @DisplayName("Integration Tests")
    class IntegrationTests {

        @Test
        @DisplayName("Should handle complete echo response workflow")
        void testCompleteEchoResponseWorkflow() throws Exception {
            // Setup
            byte[] buffer = new byte[1024];
            int bufferIndex = 64;

    protected int maxDataCount;
    /** Maximum number of setup words the server should return */
    protected byte maxSetupCount;
    /** Timeout in milliseconds to wait for the transaction to complete */
    protected int timeout = 0;
    /** Number of setup words in this request */
    protected int setupCount = 1;
    private byte subCommand;
    /** The transaction name for named pipe transactions */

        req.encode(buffer, 0);

        // Then
        byte[] pathBytes = simplePath.getBytes(StandardCharsets.UTF_16LE);
        int bodyOffset = Smb2Constants.SMB2_HEADER_LENGTH;

        // Verify complete structure
        assertEquals(9, SMBUtil.readInt2(buffer, bodyOffset)); // Structure size
        assertEquals(0, SMBUtil.readInt2(buffer, bodyOffset + 2)); // Tree flags

Puedes añadir más de un manejador de eventos.

Y tu aplicación no comenzará a recibir requests hasta que todos los manejadores de eventos `startup` hayan completado.

### Evento `shutdown`

Para añadir una función que debería ejecutarse cuando la aplicación se esté cerrando, declárala con el evento `"shutdown"`:

{* ../../docs_src/events/tutorial002.py hl[6] *}

#### Secure Erasure and Locking

	w.Header()[xhttp.ETag] = []string{"\"" + etag + "\""}
	hash.TransferChecksumHeader(w, r)

	writeSuccessResponseHeadersOnly(w)
}

// CompleteMultipartUploadHandler - Complete multipart upload.
func (api objectAPIHandlers) CompleteMultipartUploadHandler(w http.ResponseWriter, r *http.Request) {
	ctx := newContext(r, w, "CompleteMultipartUpload")