To update the configuration, use `mc admin config get` command to get the current configuration.

```sh
$ mc admin config get myminio/ notify_mqtt
notify_mqtt:1 broker="" password="" queue_dir="" queue_limit="0" reconnect_interval="0s"  keep_alive_interval="0s" qos="0" topic="" username=""
```

 * Implementors of this interface should extend {@link jcifs.config.BaseConfiguration} or
 * {@link jcifs.config.DelegatingConfiguration} to get forward compatibility.
 *
 * @author mbechler
 *
 */
public interface Configuration {

    /**
     * Gets the secure random number generator for cryptographic operations
     *
     * @return random source to use
     */
    SecureRandom getRandom();

    /**
     *
     *

# Path Operation Configuration { #path-operation-configuration }

There are several parameters that you can pass to your *path operation decorator* to configure it.

/// warning

Notice that these parameters are passed directly to the *path operation decorator*, not to your *path operation function*.

///

## Response Status Code { #response-status-code }

You can define the (HTTP) `status_code` to be used in the response of your *path operation*.

# Path Operation Advanced Configuration { #path-operation-advanced-configuration }

## OpenAPI operationId { #openapi-operationid }

/// warning

If you are not an "expert" in OpenAPI, you probably don't need this.

///

You can set the OpenAPI `operationId` to be used in your *path operation* with the parameter `operation_id`.

You would have to make sure that it is unique for each operation.

To configure them, pass the `swagger_ui_parameters` argument when creating the `FastAPI()` app object or to the `get_swagger_ui_html()` function.

`swagger_ui_parameters` receives a dictionary with the configurations passed to Swagger UI directly.

## Documentation Summary and Description - OpenAPI { #documentation-summary-and-description-openapi }

This topic provides commands to set up different configurations of hosts, nodes, and drives. The examples provided here can be used as a starting point for other configurations.

1. [Standalone Deployment](#standalone-deployment)
2. [Distributed Deployment](#distributed-deployment)
3. [Cloud Scale Deployment](#cloud-scale-deployment)

  - Bucket Tags
  - Bucket Object-Lock configurations (including retention and legal hold configuration)
  - Bucket Encryption configuration

> NOTE: Bucket versioning is automatically enabled for all new and existing buckets on all replicated sites.

The following Bucket features will **not be replicated**, is designed to differ between sites:

- Bucket notification configuration
- Bucket lifecycle (ILM) configuration

        assertEquals("30s", fessConfig.getCrawlerHotthreadTimeout());
        assertEquals("cpu", fessConfig.getCrawlerHotthreadType());
    }

    // Test field name configurations
    public void test_fieldNameConfigurations() {
        // Test all field name configurations are properly returned
        assertNotNull(fessConfig.getIndexFieldFavoriteCount());
        assertNotNull(fessConfig.getIndexFieldClickCount());

        }

        @Test
        @DisplayName("Should handle multiple configurations")
        void testMultipleConfigurations() throws SMBProtocolDecodingException {
            // Given - create multiple configurations
            Configuration config1 = mock(Configuration.class);
            Configuration config2 = mock(Configuration.class);

            Smb2LockResponse response1 = new Smb2LockResponse(config1);