sources | indent 10 }} {{- end }} minio/templates/post-install-create-user-job.yaml {{- if .Values.users }} apiVersion: batch/v1 kind: Job metadata: name: {{ template "minio.fullname" . }}-make-user-job namespace: {{ .Release.Namespace | quote }} labels: app: {{ template "minio.name" . }}-make-user-job chart: {{ template "minio.chart" . }} release: {{ .Release.Name }} heritage: {{ .Release.Service }} annotations: "helm.sh/hook": post-install,post-upgrade "helm.sh/hook-delete-policy": hook-succee...

sources | indent 10 }} {{- end }} minio/templates/post-install-create-user-job.yaml {{- if .Values.users }} apiVersion: batch/v1 kind: Job metadata: name: {{ template "minio.fullname" . }}-make-user-job namespace: {{ .Release.Namespace | quote }} labels: app: {{ template "minio.name" . }}-make-user-job chart: {{ template "minio.chart" . }} release: {{ .Release.Name }} heritage: {{ .Release.Service }} annotations: "helm.sh/hook": post-install,post-upgrade "helm.sh/hook-delete-policy": hook-succee...

sources | indent 10 }} {{- end }} minio/templates/post-install-create-user-job.yaml {{- if .Values.users }} apiVersion: batch/v1 kind: Job metadata: name: {{ template "minio.fullname" . }}-make-user-job namespace: {{ .Release.Namespace | quote }} labels: app: {{ template "minio.name" . }}-make-user-job chart: {{ template "minio.chart" . }} release: {{ .Release.Name }} heritage: {{ .Release.Service }} annotations: "helm.sh/hook": post-install,post-upgrade "helm.sh/hook-delete-policy": hook-succee...

/// info | Información

Para enviar datos, deberías usar uno de estos métodos: `POST` (el más común), `PUT`, `DELETE` o `PATCH`.

Enviar un body con un request `GET` tiene un comportamiento indefinido en las especificaciones, no obstante, es soportado por FastAPI, solo para casos de uso muy complejos/extremos.

        "category_id": category_id,
        "discussion_number": discussion_number,
        "discussion_id": discussion_id,
        "comment_id": comment_id,
        "body": body,
    }
    response = httpx.post(
        github_graphql_url,
        headers=headers,
        timeout=settings.httpx_timeout,
        json={"query": query, "variables": variables, "operationName": "Q"},
    )
    if response.status_code != 200:

            Document doc1 = Document.of(pomXml);
            Document doc2 = Document.of(pomXml);

            Map<Path, Document> pomMap = new HashMap<>();
            pomMap.put(Paths.get("/project/pom1.xml"), doc1);
            pomMap.put(Paths.get("/project/pom2.xml"), doc2);

            UpgradeContext context = createMockContext();

axUnavailable }} selector: matchLabels: app: {{ template "minio.name" . }} {{- end }} minio/templates/post-job.yaml {{- if or .Values.buckets .Values.users .Values.policies .Values.customCommands .Values.svcaccts }} apiVersion: batch/v1 kind: Job metadata: name: {{ template "minio.fullname" . }}-post-job namespace: {{ .Release.Namespace | quote }} labels: app: {{ template "minio.name" . }}-post-job chart: {{ template "minio.chart" . }} release: {{ .Release.Name }} heritage: {{ .Release.Service }}...

	}
	boundary, ok := params["boundary"]
	if !ok {
		return nil, http.ErrMissingBoundary
	}
	return multipart.NewReader(r.Body, boundary), nil
}

// PostPolicyBucketHandler - POST policy
// ----------
// This implementation of the POST operation handles object creation with a specified
// signature policy in multipart/form-data
func (api objectAPIHandlers) PostPolicyBucketHandler(w http.ResponseWriter, r *http.Request) {

{{ template "minio.name" . }} {{- end }} minio/templates/post-job.yaml {{- if or .Values.buckets .Values.users .Values.policies .Values.customCommands .Values.svcaccts }} apiVersion: batch/v1 kind: Job metadata: name: {{ template "minio.fullname" . }}-post-job labels: app: {{ template "minio.name" . }}-post-job chart: {{ template "minio.chart" . }} release: {{ .Release.Name }} heritage: {{ .Release.Service }} annotations: "helm.sh/hook": post-install,post-upgrade "helm.sh/hook-delete-policy": hook...

///

Dans OpenAPI, les chemins sont des ressources, tels que /users/ ou /items/, exposées par votre API, et les opérations sont les méthodes HTTP utilisées pour manipuler ces chemins, telles que GET, POST ou DELETE. Les operationId sont des chaînes uniques facultatives utilisées pour identifier une opération d'un chemin. Vous pouvez définir l'OpenAPI `operationId` à utiliser dans votre *opération de chemin* avec le paramètre `operation_id`.