Para agregar etiquetas a tus *path operations*, y agruparlas en la interfaz de usuario de la documentación, lee la documentación para [Tutorial - Configuraciones de Path Operation - Etiquetas](../tutorial/path-operation-configuration.md#tags){.internal-link target=_blank}.

## Resumen y Descripción de Documentación - OpenAPI { #documentation-summary-and-description-openapi }

        </field>
        <field xdoc.separator="blank">
          <name>servers</name>
          <version>1.0.0+</version>
          <description>
            Configuration of server-specific settings, mainly authentication
            method. This allows configuration of authentication on a per-server
            basis.
          </description>
          <association>
            <type>Server</type>

## Описание ответа в документации — OpenAPI { #documentation-response-description-openapi }

Чтобы задать описание ответа, отображаемое в интерфейсе документации, прочитайте документацию: [Руководство — Конфигурации операций пути — Описание ответа](../tutorial/path-operation-configuration.md#response-description){.internal-link target=_blank}.

 * in the Maven configuration.
 * </p>
 *
 * <p>
 * The following are key functionalities provided by the Toolchain interface:</p><ul>
 *   <li>Access to the type of the toolchain (e.g., JDK, compiler).</li>
 *   <li>Retrieval of the specific version of the toolchain.</li>
 *   <li>Configuration of toolchain properties to match the project's requirements.</li>
 * </ul>
 *

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)

     *
     * @param config the configuration
     */
    public SmbComOpenAndXResponse(final Configuration config) {
        super(config);
    }

    /**
     * Constructs an Open AndX response with a chained response.
     *
     * @param config the configuration
     * @param andxResp the chained seek response
     */
    public SmbComOpenAndXResponse(final Configuration config, final SmbComSeekResponse andxResp) {

                <version>${teamcity.dsl.version}</version>
                <configuration>
                    <format>kotlin</format>
                    <dstDir>target/generated-configs</dstDir>
                    <contextParameters>
                        <branch>${dslContextParameter.branch}</branch>
                    </contextParameters>
                </configuration>
            </plugin>
            <plugin>

            <param>minimalVersion=4.0.0</param>
          </params>
        </configuration>
        <executions>
          <execution>
            <id>model-v3</id>
            <goals>
              <goal>velocity</goal>
            </goals>
            <phase>generate-sources</phase>
            <configuration>
              <version>4.0.99</version>
              <templates>

        // Then
        verify(mockContext).close();
    }

    @Test
    @DisplayName("Should get Configuration")
    void testGetConfig() {
        // Given
        Configuration mockConfig = mock(Configuration.class);
        when(mockContext.getConfig()).thenReturn(mockConfig);

        // When
        Configuration config = mockContext.getConfig();

        // Then
        assertEquals(mockConfig, config);

        <executions>
          <execution>
            <id>load</id>
            <phase>validate</phase>
            <configuration>
              <resourcePaths>maven-core-it.properties</resourcePaths>
              <pluginClassLoaderOutput>target/pcl.properties</pluginClassLoaderOutput>
            </configuration>
            <goals>
              <goal>load</goal>
            </goals>
          </execution>
        </executions>