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...

        url = url,
        headers = headers,
        body = body,
      )
    assertThat(request.url).isEqualTo(url)
    assertThat(request.headers).isEqualTo(headers)
    assertThat(request.method).isEqualTo("POST")
    assertThat(request.body).isEqualTo(body)
    assertThat(request.tags).isEmpty()
  }

  @Test
  fun constructorNoBody() {
    val url = "https://example.com/".toHttpUrl()

#
# In Bash we could simply go:
#
#   readarray ARGS < <( xargs -n1 <<<"$var" ) &&
#   set -- "${ARGS[@]}" "$@"
#
# but POSIX shell has neither arrays nor command substitution, so instead we
# post-process each arg (as a line of input to sed) to backslash-escape any
# character that might be a shell metacharacter, then use eval to reverse
# that process (while maintaining the separation between arguments), and wrap

To declare a **request** body, you use <a href="https://docs.pydantic.dev/" class="external-link" target="_blank">Pydantic</a> models with all their power and benefits.

/// info

To send data, you should use one of: `POST` (the more common), `PUT`, `DELETE` or `PATCH`.

Sending a body with a `GET` request has an undefined behavior in the specifications, nevertheless, it is supported by FastAPI, only for very complex/extreme use cases.

/// info

Pour envoyer de la donnée, vous devriez utiliser : `POST` (le plus populaire), `PUT`, `DELETE` ou `PATCH`.

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...

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 | "Информация"

Чтобы отправить данные, необходимо использовать один из методов: `POST` (обычно), `PUT`, `DELETE` или `PATCH`.

Отправка тела с запросом `GET` имеет неопределенное поведение в спецификациях, тем не менее, оно поддерживается FastAPI только для очень сложных/экстремальных случаев использования.