* to the methods of the delegate. For example, overriding {@link #add} alone <i>will not</i> change
 * the behavior of {@link #addAll}, which can lead to unexpected behavior. In this case, you should
 * override {@code addAll} as well, either providing your own implementation, or delegating to the
 * provided {@code standardAddAll} method.
 *

 * with the methods in {@link Futures} or, if necessary, to extend {@link AbstractFuture}.
 *
 * <p>Occasionally, an API will return a plain {@code Future} and it will be impossible to change
 * the return type. For this case, we provide a more expensive workaround in {@code
 * JdkFutureAdapters}. However, when possible, it is more efficient and reliable to create a {@code
 * ListenableFuture} directly.
 *
 * @author Sven Mawson

		secretKey  string
		// Sent body
		body []byte
		// Expected response
		expectedRespStatus int
		lifecycleResponse  []byte
		errorResponse      APIErrorResponse
		shouldPass         bool
	}{
		// Test case - 1.
		// Filter contains more than (Prefix,Tag,And) rule
		{
			method:             http.MethodPut,
			bucketName:         bucketName,
			accessKey:          creds.AccessKey,
			secretKey:          creds.SecretKey,

Using above tier, set up a lifecycle rule with transition:

```
 mc ilm add --expiry-days 365 --transition-days 45 --storage-class "AZURETIER" myminio/srcbucket
```

Note: In the case of S3, it is possible to create a tier from MinIO running in EC2 to S3 using AWS role attached to EC2 as credentials instead of accesskey/secretkey:

```

    }

    private int getKeyLength() {
        // Java 17 switch expression for cipher key length determination
        return switch (this.cipherId) {
        case CIPHER_AES_128_CCM, CIPHER_AES_128_GCM -> 16; // AES-128 ciphers use 16-byte keys
        case CIPHER_AES_256_CCM, CIPHER_AES_256_GCM -> 32; // AES-256 ciphers use 32-byte keys
        default -> throw new IllegalArgumentException("Unsupported cipher: " + this.cipherId);

Kind types: `DOCUMENT`, `QUERY`, `USER`

---

## Development Workflow

### Build Commands

```bash
mvn compile                              # Compile
mvn test                                 # Run all tests
mvn test -Dtest=SuggesterTest           # Run specific test
mvn package                              # Package JAR

/// tip | Dica

Primeiro tente com o `bump-pydantic`; se seus testes passarem e isso funcionar, então você concluiu tudo com um único comando. ✨

///

Se o `bump-pydantic` não funcionar para o seu caso, você pode usar o suporte a modelos Pydantic v1 e v2 na mesma aplicação para fazer a migração para o Pydantic v2 gradualmente.

The main difference between various MinIO-KMS deployments is the KMS implementation. The following table helps you select the right option for your use case:

| KMS                                                                                          | Purpose                                                           |

            // When & Then
            assertEquals(attributes, info.getAttributes());
        }
    }

    @Test
    @DisplayName("Test with edge case time values")
    void testWithEdgeCaseTimeValues() {
        // Test with various time values including edge cases
        long[][] timeValues = { { 0L, 0L, 0L, 0L }, // All zeros

            assertEquals(800L, SMBUtil.readInt8(buffer, EXPECTED_SIZE * 2 + 8));
            assertEquals(900, SMBUtil.readInt4(buffer, EXPECTED_SIZE * 2 + 16));
        }
    }

    @Nested
    @DisplayName("Edge Case Tests")
    class EdgeCaseTests {

        @Test
        @DisplayName("Should handle encoding with minimum buffer size")
        void testMinimumBufferSize() {
            // Given