* This enum is used to differentiate between various SSO operations,
 * such as metadata requests and logout actions.
 */
public enum SsoResponseType {
    /**
     * Indicates a request for SSO metadata, which is typically used for
     * configuration and discovery in protocols like SAML.
     */
    METADATA,

    /**
     * Indicates a request to perform a logout operation, terminating the

 * under the License.
 */
package org.apache.maven.artifact.metadata;

import org.apache.maven.artifact.Artifact;

/**
 * AbstractArtifactMetadata
 */
@Deprecated
public abstract class AbstractArtifactMetadata
        extends org.apache.maven.repository.legacy.metadata.AbstractArtifactMetadata
        implements org.apache.maven.artifact.metadata.ArtifactMetadata {
    protected AbstractArtifactMetadata(Artifact artifact) {

echo "Stat minio2/test-bucket/defpartsize"
./mc stat --no-list minio2/test-bucket/defpartsize --insecure --json
stat_out2_rep=$(./mc stat --no-list minio2/test-bucket/defpartsize --insecure --json)
rep_obj2_algo=$(echo "${stat_out2_rep}" | jq '.metadata."X-Amz-Server-Side-Encryption"')
rep_obj2_keyid=$(echo "${stat_out2_rep}" | jq '.metadata."X-Amz-Server-Side-Encryption-Aws-Kms-Key-Id"')

    <groupId>org.apache.maven</groupId>
    <artifactId>maven-api</artifactId>
    <version>4.1.0-SNAPSHOT</version>
  </parent>

  <artifactId>maven-api-metadata</artifactId>

  <name>Maven 4 API :: Repository Metadata</name>
  <description>Maven 4 API - Immutable Repository Metadata model.</description>

  <dependencies>
    <dependency>
      <groupId>org.apache.maven</groupId>
      <artifactId>maven-api-annotations</artifactId>

 * KIND, either express or implied.  See the License for the
 * specific language governing permissions and limitations
 * under the License.
 */
package org.apache.maven.artifact.metadata;

import javax.inject.Inject;
import javax.inject.Named;
import javax.inject.Singleton;

import java.util.HashSet;
import java.util.List;
import java.util.Set;

import org.apache.maven.artifact.Artifact;

# Body - Fields { #body-fields }

The same way you can declare additional validation and metadata in *path operation function* parameters with `Query`, `Path` and `Body`, you can declare validation and metadata inside of Pydantic models using Pydantic's `Field`.

## Import `Field` { #import-field }

First, you have to import it:

{* ../../docs_src/body_fields/tutorial001_an_py310.py hl[4] *}


/// warning

func (fi FileInfo) IsCompressed() bool {
	_, ok := fi.Metadata[ReservedMetadataPrefix+"compression"]
	return ok
}

// InlineData returns true if object contents are inlined alongside its metadata.
func (fi FileInfo) InlineData() bool {
	_, ok := fi.Metadata[ReservedMetadataPrefixLower+"inline-data"]
	// Earlier MinIO versions didn't reset "x-minio-internal-inline-data"
	// from fi.Metadata when the object was tiered. So, tiered objects

        ActionResponse result = authenticator.getResponse(SsoResponseType.METADATA);

        // Verify initial state
        assertNull(result);

        // Setup with JSON response (easier to create without LastaFlute context)
        JsonResponse<?> expectedResponse = new JsonResponse<>(new HashMap<>());
        authenticator.setResponseForType(SsoResponseType.METADATA, expectedResponse);

        // Execute

    @Override
    public void addMetadata(ArtifactMetadata metadata) {
        if (metadataMap == null) {
            metadataMap = new HashMap<>();
        }

        ArtifactMetadata m = metadataMap.get(metadata.getKey());
        if (m != null) {
            m.merge(metadata);
        } else {
            metadataMap.put(metadata.getKey(), metadata);
        }
    }

    @Override

{* ../../docs_src/request_files/tutorial001_02_an_py310.py hl[9,17] *}

## `UploadFile` with Additional Metadata { #uploadfile-with-additional-metadata }

You can also use `File()` with `UploadFile`, for example, to set additional metadata:

{* ../../docs_src/request_files/tutorial001_03_an_py39.py hl[9,15] *}

## Multiple File Uploads { #multiple-file-uploads }