authenticator.close();
        }
    }

    @Test
    @DisplayName("Test password stored as char array")
    void testPasswordStoredAsCharArray() throws Exception {
        authenticator = new NtlmPasswordAuthenticator("DOMAIN", "username", "password123");

        // Use reflection to verify password is stored as char[]
        Field passwordField = NtlmPasswordAuthenticator.class.getDeclaredField("password");

* (Optionally) use `PATCH` instead of `PUT`.
* Retrieve the stored data.
* Put that data in a Pydantic model.
* Generate a `dict` without default values from the input model (using `exclude_unset`).
    * This way you can update only the values actually set by the user, instead of overriding values already stored with default values in your model.

Using `UploadFile` has several advantages over `bytes`:

* You don't have to use `File()` in the default value of the parameter.
* It uses a "spooled" file:
    * A file stored in memory up to a maximum size limit, and after passing this limit it will be stored in disk.
* This means that it will work well for large files like images, videos, large binaries, etc. without consuming all the memory.
* You can get metadata from the uploaded file.

        byte[] key = new byte[length];
        secureRandom.nextBytes(key);
        return key;
    }

    /**
     * Clear all stored keys
     */
    public void clearAllKeys() {
        checkNotClosed();

        log.info("Clearing all stored keys");

        // Wipe all raw keys
        for (Map.Entry<String, byte[]> entry : rawKeys.entrySet()) {

    end

    rect rgba(0, 255, 255, .1)
        code ->> function: say_hi(name="Rick")
        function ->> code: return stored result
    end

    rect rgba(0, 255, 255, .1)
        code ->> function: say_hi(name="Camila")
        function ->> code: return stored result
    end
```

        // Verify password is stored correctly
        assertArrayEquals(testPassword, auth.getPasswordAsCharArray());
        assertEquals(new String(testPassword), auth.getPassword());

        // Verify that modifying original array doesn't affect stored password
        Arrays.fill(testPassword, 'Y');
        assertEquals("CharArrayPass789!", auth.getPassword());

            // Store new keys
            keyManager.storeSessionKey(encKeyId, newEncryptionKey, "AES");
            keyManager.storeSessionKey(decKeyId, newDecryptionKey, "AES");

            log.debug("Keys rotated successfully in SecureKeyManager");
        } else {
            // Securely wipe old keys
            secureWipeKeys();

            // Store new keys

 * Define clean up rules for the project.
 * See https://www.jetbrains.com/help/teamcity/teamcity-data-clean-up.html#Clean-up+Rules
 *
 * @param historyDays days number of days to store build history .
 * @param artifactsDays number of days to store artifacts. In the stored history, artifacts older than this number will be cleaned up.
 * @param artifactPatterns patterns for artifacts clean-up. If not specified, all artifacts will be removed.
 */

// Now it can read the environment variable

Hello Wade Wilson from Python
```

</div>

////

As environment variables can be set outside of the code, but can be read by the code, and don't have to be stored (committed to `git`) with the rest of the files, it's common to use them for configurations or **settings**.

        String sessionId = "test-session-1";
        keyManager.storeSessionKey(sessionId, testKey, "AES");

        SecretKey retrieved = keyManager.getSessionKey(sessionId);
        assertNotNull(retrieved, "Should retrieve stored key");
        assertArrayEquals(testKey, retrieved.getEncoded(), "Retrieved key should match");
    }

    @Test
    public void testGetRawKey() {
        String sessionId = "test-session-2";