"openapi": "3.1.0",
            "info": {"title": "FastAPI", "version": "0.1.0"},
            "paths": {
                "/{id}": {
                    "delete": {
                        "summary": "Delete Deployment",
                        "operationId": "delete_deployment__id__delete",
                        "parameters": [
                            {
                                "required": True,

     */
    CLUSTER_WITNESS,

    /**
     * Individual file server witness for standalone servers
     */
    FILE_SERVER_WITNESS,

    /**
     * Scale-out file server witness for scale-out deployments
     */
    SCALE_OUT_WITNESS,

    /**
     * DFS namespace witness for distributed file system resources
     */
    DFS_WITNESS

## Deployment Concepts { #deployment-concepts }

Let's talk again about some of the same [Deployment Concepts](concepts.md) in terms of containers.

Containers are mainly a tool to simplify the process of **building and deploying** an application, but they don't enforce a particular approach to handle these **deployment concepts**, and there are several possible strategies.

You can learn more about [FastAPI versions and how to pin and upgrade them](https://fastapi.tiangolo.com/deployment/versions/) for your project in the docs.

## Reporting a Vulnerability

# Concepts de déploiement { #deployments-concepts }

Lorsque vous déployez une application **FastAPI**, ou en fait n'importe quel type de web API, il existe plusieurs concepts qui vous importent probablement, et en les utilisant vous pouvez trouver la manière la **plus appropriée** de **déployer votre application**.

Parmi les concepts importants, on trouve :

* Sécurité - HTTPS
* Exécuter au démarrage
* Redémarrages

 * or similar ad-hoc collections of artifacts. This repository is considered read-only
 * within the context of a session, meaning it can only be used for artifact resolution,
 * not for installation or deployment. This interface does not provide direct access
 * to artifacts; that functionality is handled by a {@code WorkspaceReader}.
 */
public interface WorkspaceRepository extends Repository {

    /**

`--reload` seçeneği çok daha fazla kaynak tüketir, daha kararsızdır vb.

**Geliştirme** sırasında çok yardımcı olur, ancak **production** ortamında kullanmamalısınız.

///

## Deployment Kavramları { #deployment-concepts }

Bu örnekler server programını (ör. Uvicorn) çalıştırır; **tek bir process** başlatır, tüm IP'lerde (`0.0.0.0`) ve önceden belirlenmiş bir port'ta (ör. `80`) dinler.

 */
package org.apache.maven.internal.transformation;

import java.io.IOException;

import org.apache.maven.project.MavenProject;
import org.eclipse.aether.RepositorySystemSession;
import org.eclipse.aether.deployment.DeployRequest;
import org.eclipse.aether.installation.InstallRequest;

/**
 * Maven transformer manager.
 *
 * @since 4.0.0
 */
public interface TransformerManager {

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

import org.apache.maven.internal.transformation.TransformerManager;
import org.eclipse.aether.RepositorySystemSession;
import org.eclipse.aether.deployment.DeployRequest;
import org.eclipse.aether.installation.InstallRequest;
import org.eclipse.aether.spi.artifact.transformer.ArtifactTransformer;

import static java.util.Objects.requireNonNull;

/**

distributed mode: distributed ## other supported values are "standalone" ## Additional labels to include with deployment or statefulset additionalLabels: {} ## Additional annotations to include with deployment or statefulset additionalAnnotation: {} ## Typically the deployment/statefulset includes checksums of secrets/config, ## So that when these change on a subsequent helm install, the deployment/statefulset ## is restarted. This can result in unnecessary restarts under GitOps tooling such as ## flux,...