from fastapi import APIRouter, FastAPI
from fastapi.testclient import TestClient

app = FastAPI()

router_lax = APIRouter(prefix="/lax", strict_content_type=False)
router_strict = APIRouter(prefix="/strict", strict_content_type=True)
router_default = APIRouter(prefix="/default")


@router_lax.post("/items/")
async def router_lax_post(data: dict):
    return data


@router_strict.post("/items/")
async def router_strict_post(data: dict):

  An example claim validation rule expression that matches the validation automatically
  applied when username.claim is set to 'email' is 'claims.?email_verified.orValue(true) == true'. 
  By explicitly comparing the value to true, we let type-checking see the result will be a boolean, 

{{/* 2 extra rounds for 256-bit keys. */}} Lenc256: {{- template "load_keys" (load_keys_args 0 2) }} {{- template "enc" (enc_args 0 $N true) }} {{- template "enc" (enc_args 1 $N true) }} {{/* 2 extra rounds for 192-bit keys. */}} Lenc192: {{- template "load_keys" (load_keys_args 2 2) }} {{- template "enc" (enc_args 2 $N true) }} {{- template "enc" (enc_args 3 $N true) }} {{/* 10 rounds for 128-bit (with special handling for final). */}} Lenc128: {{- template "load_keys" (load_keys_args 4 11) }} {{-...

                        "summary": "A",
                        "operationId": "a_a__id__get",
                        "parameters": [
                            {
                                "required": True,
                                "schema": {"title": "Id"},
                                "name": "id",
                                "in": "path",
                            }
                        ],

                        "operationId": "read_item_items__item_id__get",
                        "parameters": [
                            {
                                "required": True,
                                "schema": {"title": "Item Id", "type": "string"},
                                "name": "item_id",
                                "in": "path",
                            },

- Add a `serving` and `terminating` condition to the EndpointSlice API.
  `serving` tracks the readiness of endpoints regardless of their terminating state. This is distinct from `ready` since `ready` is only true when pods are not terminating. 

                                    "schema": {"$ref": "#/components/schemas/Product"}
                                }
                            },
                            "required": True,
                        },
                        "responses": {
                            "200": {
                                "description": "Successful Response",

                        "parameters": [
                            {
                                "in": "header",
                                "name": "someheader",
                                "required": True,
                                "schema": {"title": "Someheader", "type": "string"},
                            }
                        ],
                        "responses": {
                            "200": {

https://www.external.org/events/invoices/2expen51ve
```

그리고 다음과 같은 JSON body를 포함할 것입니다:

```JSON
{
    "description": "Payment celebration",
    "paid": true
}
```

또한 그 *external API*로부터 다음과 같은 JSON body 응답을 기대합니다:

```JSON
{
    "ok": true
}
```

/// tip | 팁

- Pods which set `hostNetwork: true` and declare ports, get the `hostPort` field set automatically. Previously this would happen in the PodTemplate of a Deployment, DaemonSet or other workload API.  Now `hostPort` will only be set when an actual Pod is being created.  If this presents a problem, setting the feature gate "DefaultHostNetworkHostPortsInPodTemplates" to true will revert this behavior.  Please file a kubernetes bug if you need to do this....