values my-release > old_values.yaml ``` Then change the field `image.tag` in `old_values.yaml` file with MinIO image tag you want to use. Now update the chart using ```bash helm upgrade -f old_values.yaml my-release minio/minio ``` Default upgrade strategies are specified in the `values.yaml` file. Update these fields if you'd like to use a different strategy. ### Configuration Refer the [Values file](./values.yaml) for all the possible config fields. You can specify each parameter using the `--set k...

values my-release > old_values.yaml ``` Then change the field `image.tag` in `old_values.yaml` file with MinIO image tag you want to use. Now update the chart using ```bash helm upgrade -f old_values.yaml my-release minio/minio ``` Default upgrade strategies are specified in the `values.yaml` file. Update these fields if you'd like to use a different strategy. ### Configuration Refer the [Values file](./values.yaml) for all the possible config fields. You can specify each parameter using the `--set k...

        verify(mockContext).getConfig();
    }

    @Test
    @DisplayName("Test writeBytesWireFormat with all fields set")
    void testWriteBytesWireFormatComplete() {
        request = new Smb2QueryDirectoryRequest(mockConfig);

        // Set all fields
        byte[] fileId = new byte[16];
        for (int i = 0; i < 16; i++) {
            fileId[i] = (byte) (i * 2);
        }

	xhttp "github.com/minio/minio/internal/http"
)

// Version - represents the current version of audit log structure.
const Version = "1"

// NewEntry - constructs an audit entry object with some fields filled
func NewEntry(deploymentID string) audit.Entry {
	return audit.Entry{
		Version:      Version,
		DeploymentID: deploymentID,
		Time:         time.Now().UTC(),
	}
}

values my-release > old_values.yaml ``` Then change the field `image.tag` in `old_values.yaml` file with MinIO image tag you want to use. Now update the chart using ```bash helm upgrade -f old_values.yaml my-release minio/minio ``` Default upgrade strategies are specified in the `values.yaml` file. Update these fields if you'd like to use a different strategy. ### Configuration Refer the [Values file](./values.yaml) for all the possible config fields. You can specify each parameter using the `--set k...

labels: ["type=defect"]
body:
  - type: markdown
    attributes:
      value: >
        Thank you for filing a bug report. Please help us identify and resolve the bug by filling
        out the following fields. Before we begin, please make sure that the bug is still present in
        the [latest](https://github.com/google/guava/releases/latest) version of Guava available.

Sie können dies in der Dokumentations-UI unter `/docs` testen:

<div class="screenshot">
<img src="/img/tutorial/request-form-models/image01.png">
</div>

## Zusätzliche Formularfelder verbieten { #forbid-extra-form-fields }

<div class="screenshot">
<img src="/img/tutorial/request-form-models/image01.png">
</div>

## Interdire les champs de formulaire supplémentaires { #forbid-extra-form-fields }

Dans certains cas d'utilisation particuliers (probablement peu courants), vous pourriez vouloir **restreindre** les champs de formulaire à ceux déclarés dans le modèle Pydantic, et **interdire** tout champ **supplémentaire**.

        SMBUtil.writeInt2(4, buffer, 0);
        // Write reserved field (any value is acceptable)
        buffer[2] = (byte) byte2;
        buffer[3] = (byte) byte3;

        // When
        int bytesRead = response.readBytesWireFormat(buffer, 0);

        // Then - should still read 4 bytes regardless of reserved field value
        assertEquals(4, bytesRead);
    }

    @Test

            verify(mockTree).send(cap.capture(), any(RequestParam.class));
            Smb2ReadRequest req = cap.getValue();

            // Reflectively inspect the private 'offset' field to assert it used the advanced fp
            Field offField = Smb2ReadRequest.class.getDeclaredField("offset");
            offField.setAccessible(true);
            long offVal = offField.getLong(req);