id: generics-proposal
    attributes:
      label: Is this about generics?
      description: If so, how does this relate to the accepted design and other generics proposals?
      placeholder: |
       Yes or No

       If yes, 
        1. how does this relate to the accepted design and other generics proposals?

    validations:
      required: true

  - type: textarea
    id: proposal
    attributes:

- fastapi-people.md
- Resources:
  - resources/index.md
  - project-generation.md
  - external-links.md
  - newsletter.md
- About:
  - about/index.md
  - alternatives.md
  - history-design-future.md
  - benchmarks.md
- Help:
  - help/index.md
  - help-fastapi.md
  - contributing.md
- release-notes.md
markdown_extensions:
  toc:
    permalink: true
  markdown.extensions.codehilite:

  German:
  - author: Marcel Sander (actidoo)
    author_link: https://www.actidoo.com
    link: https://www.actidoo.com/de/blog/python-fastapi-domain-driven-design
    title: Domain-driven Design mit Python und FastAPI
  - author: Nico Axtmann
    author_link: https://twitter.com/_nicoax
    link: https://blog.codecentric.de/2019/08/inbetriebnahme-eines-scikit-learn-modells-mit-onnx-und-fastapi/

demo.datadetect.com demo.jelastic.com democracia.bo democrat demon.nl denmark.museum deno-staging.dev deno.dev dental dentist dep.no deporte.bo depot.museum des.br desa.id desi design design.aero design.museum det.br deta.app deta.dev detroit.museum dev dev-myqnapcloud.com dev.br dev.static.land dev.vu development.run devices.resinstaging.io df.gov.br df.leg.br dgca.aero dh.bytemark.co.uk dhl diadem.cloud diamonds dielddanuorri.no diet digick.jp digital dinosaur.museum direct direct.quickconnect.cn direct.quickconnect.to...

name: 'Auto Assign PR to Author'
on:
  pull_request:
    types: [opened]

permissions:
  contents: read

jobs:
  add-reviews:
    permissions:
      contents: read  # for kentaro-m/auto-assign-action to fetch config file
      pull-requests: write  # for kentaro-m/auto-assign-action to assign PR reviewers
    runs-on: ubuntu-latest
    steps:

  "caBundle" .Values.istiodRemote.injectionCABundle
  "namespace" .Release.Namespace }}
{{- define "core" }}
{{- /* Kubernetes unfortunately requires a unique name for the webhook in some newer versions, so we assign
a unique prefix to each. */}}
- name: {{.Prefix}}sidecar-injector.istio.io
  clientConfig:
    {{- if .injectionURL }}
    url: "{{ .injectionURL }}"
    {{- else }}
    service:

						</div>
					</div>
					<div class="text-center">
						<button type="submit" name="login"
							class="btn btn-primary btn-block"
							value="<la:message key="labels.login"/>">
							<em class="fa fa-sign-in">
							<la:message key="labels.login" />
						</button>
					</div>
				</la:form>
			</div>
		</div>
	</div>
	<input type="hidden" id="contextPath" value="${contextPath}" />

# ==============================================================================

name: Trusted Partner PR
on:
  pull_request_target:

permissions:
  contents: read

jobs:
  assign-partner-tags:
    runs-on: ubuntu-latest
    permissions:
      # Needed to attach tags into the PR
      issues: write
      contents: write
      pull-requests: write
    if: |

{{/* affinity - https://kubernetes.io/docs/concepts/configuration/assign-pod-node/ */}} {{ define "nodeaffinity" }} nodeAffinity: requiredDuringSchedu: {{- include "nodeAffinityRequired" . }} preferredDuringSched: {{- include "nodeAffinityPreferre" . }} {{- end }} {{- define "nodeAffinityRequired" }} {{- $nodeSelector := default .global.defaultNodeSelector .nodeSelector -}} {{- if or .global.arch $nodeSelector }} nodeSelectorTerms: - matchExpressions: {{- if .global.arch }} - key: kubernetes.io/arch...

global.jwtPolicy=first-party-jwt ``` manifests/charts/UPDATING-CHARTS.md # Updating charts and values.yaml ## Acceptable Pull Requests Helm charts `values.yaml` represent a complex user facing API that tends to grow uncontrollably over time due to design choices in Helm. The underlying Kubernetes resources we configure have 1000s of fields; given enough users and bespoke use cases, eventually someone will want to customize every one of those fields. If all fields are exposed in `values.yaml`, we end...