{!> ../../docs_src/security/tutorial003.py!}
```

////

#### About `**user_dict`

`UserInDB(**user_dict)` means:

*Pass the keys and values of the `user_dict` directly as key-value arguments, equivalent to:*

```Python
UserInDB(
    username = user_dict["username"],
    email = user_dict["email"],
    full_name = user_dict["full_name"],
    disabled = user_dict["disabled"],

{!> ../../docs_src/security/tutorial003.py!}
```

////

#### Über `**user_dict`

`UserInDB(**user_dict)` bedeutet:

*Übergib die Schlüssel und Werte des `user_dict` direkt als Schlüssel-Wert-Argumente, äquivalent zu:*

```Python
UserInDB(
    username = user_dict["username"],
    email = user_dict["email"],
    full_name = user_dict["full_name"],
    disabled = user_dict["disabled"],

	// All unique drives for this deployment
	globalEndpoints EndpointServerPools
	// All unique nodes for this deployment
	globalNodes []Node

	// The name of this local node, fetched from arguments
	globalLocalNodeName    string
	globalLocalNodeNameHex string
	globalNodeNamesHex     = make(map[string]struct{})

	// The global subnet config
	globalSubnetConfig subnet.Config

`values.yaml` file. Update these fields if you'd like to use a different strategy. Configuration ---------- Refer the [Values file](./values.yaml) for all the possible config fields. You can specify each parameter using the `--set key=value[,key=value]` argument to `helm install`. For example, ```bash helm install --name my-release --set persistence.size=1Ti minio/minio ``` The above command deploys MinIO server with a 1Ti backing persistent volume. Alternately, you can provide a YAML file that specifies...

`values.yaml` file. Update these fields if you'd like to use a different strategy. Configuration ---------- Refer the [Values file](./values.yaml) for all the possible config fields. You can specify each parameter using the `--set key=value[,key=value]` argument to `helm install`. For example, ```bash helm install --name my-release --set persistence.size=1Ti minio/minio ``` The above command deploys MinIO server with a 1Ti backing persistent volume. Alternately, you can provide a YAML file that specifies...

`values.yaml` file. Update these fields if you'd like to use a different strategy. Configuration ---------- Refer the [Values file](./values.yaml) for all the possible config fields. You can specify each parameter using the `--set key=value[,key=value]` argument to `helm install`. For example, ```bash helm install --name my-release --set persistence.size=1Ti minio/minio ``` The above command deploys MinIO server with a 1Ti backing persistent volume. Alternately, you can provide a YAML file that specifies...

`values.yaml` file. Update these fields if you'd like to use a different strategy. Configuration ---------- Refer the [Values file](./values.yaml) for all the possible config fields. You can specify each parameter using the `--set key=value[,key=value]` argument to `helm install`. For example, ```bash helm install --name my-release --set persistence.size=1Ti minio/minio ``` The above command deploys MinIO server with a 1Ti backing persistent volume. Alternately, you can provide a YAML file that specifies...

`values.yaml` file. Update these fields if you'd like to use a different strategy. Configuration ---------- Refer the [Values file](./values.yaml) for all the possible config fields. You can specify each parameter using the `--set key=value[,key=value]` argument to `helm install`. For example, ```bash helm install --name my-release --set persistence.size=1Ti minio/minio ``` The above command deploys MinIO server with a 1Ti backing persistent volume. Alternately, you can provide a YAML file that specifies...

`values.yaml` file. Update these fields if you'd like to use a different strategy. Configuration ---------- Refer the [Values file](./values.yaml) for all the possible config fields. You can specify each parameter using the `--set key=value[,key=value]` argument to `helm install`. For example, ```bash helm install --name my-release --set persistence.size=1Ti minio/minio ``` The above command deploys MinIO server with a 1Ti backing persistent volume. Alternately, you can provide a YAML file that specifies...

`values.yaml` file. Update these fields if you'd like to use a different strategy. Configuration ---------- Refer the [Values file](./values.yaml) for all the possible config fields. You can specify each parameter using the `--set key=value[,key=value]` argument to `helm install`. For example, ```bash helm install --name my-release --set persistence.size=1Ti minio/minio ``` The above command deploys MinIO server with a 1Ti backing persistent volume. Alternately, you can provide a YAML file that specifies...