///

## What it does { #what-it-does }

It will go and look in the request for that `Authorization` header, check if the value is `Bearer ` plus some token, and will return the token as a `str`.

"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-succeeded,before-hook-creation {{- with .Values.postJob.annotations }} {{- toYaml . | nindent 4 }} {{- end }} spec: template: metadata: labels: app: {{ template "minio.name" . }}-job release: {{ .Release.Name }} {{- if .Values.podLabels...

"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-succeeded,before-hook-creation {{- with .Values.postJob.annotations }} {{- toYaml . | nindent 4 }} {{- end }} spec: template: metadata: labels: app: {{ template "minio.name" . }}-job release: {{ .Release.Name }} {{- if .Values.podLabels...

{{ .Release.Namespace | quote }} 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-succeeded,before-hook-creation {{- with .Values.postJob.annotations }} {{- toYaml . | nindent 4 }} {{- end }} spec: template: metadata: labels: app: {{ template "minio.name" . }}-job release: {{ .Release.Name }} {{- if .Values.podLabels...

{{ .Release.Namespace | quote }} 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-succeeded,before-hook-creation {{- with .Values.postJob.annotations }} {{- toYaml . | nindent 4 }} {{- end }} spec: template: metadata: labels: app: {{ template "minio.name" . }}-job release: {{ .Release.Name }} {{- if .Values.podLabels...

{{ .Release.Namespace | quote }} 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-succeeded,before-hook-creation {{- with .Values.postJob.annotations }} {{- toYaml . | nindent 4 }} {{- end }} spec: template: metadata: labels: app: {{ template "minio.name" . }}-job release: {{ .Release.Name }} {{- if .Values.podLabels...

"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-succeeded,before-hook-creation {{- with .Values.postJob.annotations }} {{- toYaml . | nindent 4 }} {{- end }} spec: template: metadata: labels: app: {{ template "minio.name" . }}-job release: {{ .Release.Name }} {{- if .Values.podLabels...

This could be especially useful during testing, as it's very easy to override a dependency with your own custom settings.

### The config file { #the-config-file }

Coming from the previous example, your `config.py` file could look like:

{* ../../docs_src/settings/app02_an_py39/config.py hl[10] *}

Notice that now we don't create a default instance `settings = Settings()`.

### The main app file { #the-main-app-file }

## Pydantic

すべてのデータバリデーションは <a href="https://docs.pydantic.dev/" class="external-link" target="_blank">Pydantic</a> によって内部で実行されるため、Pydanticの全てのメリットが得られます。そして、安心して利用することができます。

`str`、 `float` 、 `bool` および他の多くの複雑なデータ型を型宣言に使用できます。

これらのいくつかについては、チュートリアルの次の章で説明します。

## 順序の問題

*path operations* を作成する際、固定パスをもつ状況があり得ます。

`/users/me` から、現在のユーザに関するデータを取得するとします。

    examples/jars/spark-examples*.jar 10
```

The job should produce an output as shown below. Note the value of pi in the output.

```
17/03/22 23:21:10 INFO DAGScheduler: Job 0 finished: reduce at SparkPi.scala:38, took 1.302805 s
Pi is roughly 3.1445191445191445
```

Job status can also be viewed in a browser by navigating to the YARN ResourceManager Web UI and clicking on job history server information.

### **4.2 WordCount**