WolfEYc

Set kube active namespace

kubectl config set-context (kubectl config current-context) --namespace=observability

create secret 

kubectl create secret generic mysecret --from-literal=username=admin --from-literal=password=s3cr3t

WolfEYc

import asyncio
from contextlib import asynccontextmanager

import oracledb
import pytest
import pytest_asyncio
from asgi_lifespan import LifespanManager
from fastapi import FastAPI
from httpx import AsyncClient
from oracledb import AsyncConnectionPool

WolfEYc

import asyncio
import re
from contextlib import asynccontextmanager
from functools import reduce
from itertools import chain
from operator import itemgetter
from typing import Any, Coroutine, Iterable, NamedTuple, Optional

import oracledb
import polars as pl

WolfEYc

 1. Design your schema based on how data is used, not based on how it's stored.
 
 2. FE devs have more freedom to pick and choose what fields they want, 
 instead of being stuck to the fields of the Rest API
 and wait for a data engineer to update or create Yet Another™ endpoint.
 
 3. FE devs can rename fields to what they want to consume it as on the FE in their request,
 instead of having to manually parse and rename the json response.
 
 4. Data Engineers will spend less time changing or adding queries over the same data,