Search Options

Results per page
Sort
Preferred Languages
Advance

Results 151 - 160 of 254 for YAML (0.03 sec)

  1. helm-releases/minio-4.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 each...
    Registered: Sun Dec 28 19:28:13 UTC 2025
    - Last Modified: Mon May 02 06:10:34 UTC 2022
    - 18K bytes
    - Viewed (0)
  2. helm-releases/minio-4.0.4.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: Thu Jul 14 04:44:23 UTC 2022
    - 18.2K bytes
    - Viewed (0)
  3. helm-releases/minio-4.0.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 each...
    Registered: Sun Dec 28 19:28:13 UTC 2025
    - Last Modified: Wed Aug 03 06:10:44 UTC 2022
    - 18.6K bytes
    - Viewed (0)
  4. helm-reindex.sh

    #!/bin/bash
    
    helm package helm/minio -d helm-releases/
    
    Registered: Sun Dec 28 19:28:13 UTC 2025
    - Last Modified: Fri Aug 20 22:30:54 UTC 2021
    - 121 bytes
    - Viewed (0)
  5. helm-releases/minio-4.0.14.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 Sep 05 01:06:49 UTC 2022
    - 19.6K bytes
    - Viewed (0)
  6. helm-releases/minio-4.0.7.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: Thu Jul 28 03:54:38 UTC 2022
    - 18.6K bytes
    - Viewed (0)
  7. helm-releases/minio-4.0.10.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: Thu Aug 04 16:09:22 UTC 2022
    - 19.2K bytes
    - Viewed (0)
  8. .editorconfig

    charset = utf-8
    trim_trailing_whitespace = true
    insert_final_newline = true
    
    spelling_languages = en-US
    
    # Markdown files sometimes need trailing whitespaces.
    [*.md]
    trim_trailing_whitespace = false
    
    [*.{yml,yaml}]
    indent_size = 2
    
    [gradle/verification-metadata.xml]
    indent_size = 3
    
    [subprojects/launcher/src/main/resources/release-features.txt]
    Registered: Wed Dec 31 11:36:14 UTC 2025
    - Last Modified: Tue Nov 25 07:01:54 UTC 2025
    - 582 bytes
    - Viewed (0)
  9. .github/labeler.yml

            - '!pyproject.toml'
    
    internal:
      - all:
        - changed-files:
          - any-glob-to-any-file:
            - .github/**
            - scripts/**
            - .gitignore
            - .pre-commit-config.yaml
            - pdm_build.py
            - requirements*.txt
            - docs/en/data/sponsors.yml
            - docs/en/overrides/main.html
          - all-globs-to-all-files:
            - '!docs/*/docs/**'
            - '!fastapi/**'
    Registered: Sun Dec 28 07:19:09 UTC 2025
    - Last Modified: Sun Nov 23 20:10:04 UTC 2025
    - 921 bytes
    - Viewed (0)
  10. docs/ru/docs/advanced/path-operation-advanced-configuration.md

    Затем мы работаем с запросом напрямую и извлекаем тело как `bytes`. Это означает, что FastAPI даже не попытается распарсить полезную нагрузку запроса как JSON.
    
    А затем в нашем коде мы напрямую парсим этот YAML и снова используем ту же Pydantic-модель для валидации YAML-содержимого:
    
    //// tab | Pydantic v2
    
    Registered: Sun Dec 28 07:19:09 UTC 2025
    - Last Modified: Wed Dec 17 20:41:43 UTC 2025
    - 11.5K bytes
    - Viewed (0)
Back to top