- Sort Score
- Result 10 results
- Languages All
Results 71 - 80 of 254 for YAML (0.07 sec)
-
docs_src/path_operation_advanced_configuration/tutorial007_pv1_py39.py
raw_body = await request.body() try: data = yaml.safe_load(raw_body) except yaml.YAMLError: raise HTTPException(status_code=422, detail="Invalid YAML") try: item = Item.parse_obj(data) except ValidationError as e: raise HTTPException(status_code=422, detail=e.errors())
Registered: Sun Dec 28 07:19:09 UTC 2025 - Last Modified: Sat Dec 20 15:55:38 UTC 2025 - 767 bytes - Viewed (0) -
docs_src/path_operation_advanced_configuration/tutorial007_py39.py
raw_body = await request.body() try: data = yaml.safe_load(raw_body) except yaml.YAMLError: raise HTTPException(status_code=422, detail="Invalid YAML") try: item = Item.model_validate(data) except ValidationError as e: raise HTTPException(status_code=422, detail=e.errors(include_url=False))
Registered: Sun Dec 28 07:19:09 UTC 2025 - Last Modified: Wed Dec 10 08:55:32 UTC 2025 - 797 bytes - Viewed (0) -
helm-releases/minio-4.0.11.tgz
command: ```bash helm get values my-release > old_values.yaml ``` Then change the field `image.tag` in `old_values.yaml` file with MinIO image tag you want to use. Now update the chart using ```bash helm upgrade -f old_values.yaml my-release minio/minio ``` Default upgrade strategies are specified in the `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...
Registered: Sun Dec 28 19:28:13 UTC 2025 - Last Modified: Sun Aug 07 05:41:47 UTC 2022 - 19.2K bytes - Viewed (0) -
helm-releases/minio-4.0.2.tgz
command: ```bash helm get values my-release > old_values.yaml ``` Then change the field `image.tag` in `old_values.yaml` file with MinIO image tag you want to use. Now update the chart using ```bash helm upgrade -f old_values.yaml my-release minio/minio ``` Default upgrade strategies are specified in the `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...
Registered: Sun Dec 28 19:28:13 UTC 2025 - Last Modified: Mon May 09 04:25:47 UTC 2022 - 18K bytes - Viewed (0) -
helm-releases/minio-4.0.3.tgz
command: ```bash helm get values my-release > old_values.yaml ``` Then change the field `image.tag` in `old_values.yaml` file with MinIO image tag you want to use. Now update the chart using ```bash helm upgrade -f old_values.yaml my-release minio/minio ``` Default upgrade strategies are specified in the `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...
Registered: Sun Dec 28 19:28:13 UTC 2025 - Last Modified: Fri Jul 08 06:16:22 UTC 2022 - 18K bytes - Viewed (0) -
helm-releases/minio-3.1.3.tgz
command: ```bash helm get values my-release > old_values.yaml ``` Then change the field `image.tag` in `old_values.yaml` file with MinIO image tag you want to use. Now update the chart using ```bash helm upgrade -f old_values.yaml my-release minio/minio ``` Default upgrade strategies are specified in the `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...
Registered: Sun Dec 28 19:28:13 UTC 2025 - Last Modified: Sat Sep 18 18:09:59 UTC 2021 - 14.4K bytes - Viewed (0) -
cmd/batch-replicate_test.go
` var job BatchJobRequest err := yaml.Unmarshal([]byte(replicateYaml), &job) if err != nil { t.Fatal("Failed to parse batch-job-replicate yaml", err) } if !slices.Equal(job.Replicate.Source.Prefix.F(), []string{"object-prefix1"}) { t.Fatal("Failed to parse batch-job-replicate yaml", err) } multiPrefixReplicateYaml := ` replicate: apiVersion: v1
Registered: Sun Dec 28 19:28:13 UTC 2025 - Last Modified: Thu Aug 01 12:53:30 UTC 2024 - 7.9K bytes - Viewed (0) -
helm-releases/minio-3.0.1.tgz
command: ```bash helm get values my-release > old_values.yaml ``` Then change the field `image.tag` in `old_values.yaml` file with MinIO image tag you want to use. Now update the chart using ```bash helm upgrade -f old_values.yaml my-release minio/minio ``` Default upgrade strategies are specified in the `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...
Registered: Sun Dec 28 19:28:13 UTC 2025 - Last Modified: Thu Sep 02 01:47:43 UTC 2021 - 13.8K bytes - Viewed (0) -
helm-releases/minio-3.0.2.tgz
command: ```bash helm get values my-release > old_values.yaml ``` Then change the field `image.tag` in `old_values.yaml` file with MinIO image tag you want to use. Now update the chart using ```bash helm upgrade -f old_values.yaml my-release minio/minio ``` Default upgrade strategies are specified in the `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...
Registered: Sun Dec 28 19:28:13 UTC 2025 - Last Modified: Fri Sep 03 08:11:32 UTC 2021 - 13.8K bytes - Viewed (0) -
helm-releases/minio-3.1.9.tgz
command: ```bash helm get values my-release > old_values.yaml ``` Then change the field `image.tag` in `old_values.yaml` file with MinIO image tag you want to use. Now update the chart using ```bash helm upgrade -f old_values.yaml my-release minio/minio ``` Default upgrade strategies are specified in the `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...
Registered: Sun Dec 28 19:28:13 UTC 2025 - Last Modified: Sun Oct 10 21:28:04 UTC 2021 - 14.6K bytes - Viewed (0)