Notice that the input model is still validated.

So, if you want to receive partial updates that can omit all the attributes, you need to have a model with all the attributes marked as optional (with default values or `None`).

To distinguish from the models with all optional values for **updates** and models with required values for **creation**, you can use the ideas described in [Extra Models](extra-models.md){.internal-link target=_blank}.

        jvmArgumentProviders.add(CiEnvironmentProvider(this))
        runWithJavaVersion(JavaLanguageVersion.of(project.testJavaVersion))

        if (name != "archTest") {
            // TODO distinguish archTest and other tests
            addOsAsInputs()
        }
        configureRerun()

        if (BuildEnvironment.isCiServer) {
            develocity.testRetry {

          <version>3.0.0+</version>
          <required>true</required>
          <description>
            A universally unique identifier for a project. It is normal to
            use a fully-qualified package name to distinguish it from other
            projects with a similar name (eg. {@code org.apache.maven}).
          </description>
          <type>String</type>
        </field>
        <field>
          <name>artifactId</name>

Entonces, si deseas recibir actualizaciones parciales que puedan omitir todos los atributos, necesitas tener un modelo con todos los atributos marcados como opcionales (con valores por defecto o `None`).

Para distinguir entre los modelos con todos los valores opcionales para **actualizaciones** y modelos con valores requeridos para **creación**, puedes utilizar las ideas descritas en [Modelos Extra](extra-models.md){.internal-link target=_blank}.

     * Used in conjunction with the admin security principal.
     */
    @Size(max = 1000)
    public String ldapAdminSecurityCredentials;

    /**
     * LDAP base DN (Distinguished Name) for user searches.
     * Defines the root of the LDAP directory tree for user lookups.
     */
    @Size(max = 1000)
    public String ldapBaseDn;

    /**

enabled by default on listeners. Using multipathtcp="0" reverts to the
pre-Go 1.24 behavior.

Go 1.24 changed the behavior of `go test -json` to emit build errors as JSON
instead of text.
These new JSON events are distinguished by new `Action` values,
but can still cause problems with CI systems that aren't robust to these events.
This behavior can be controlled with the `gotestjsonbuildtext` setting.