Jonathan B.

for graphql and openapi, we have tox tools for regenerating these

Hi there, the generated code for phoenix can come from 3 places, changes to the graphql schema, changes to the openapi schema and in the UI these trigger corresponding UI changes via Relay

do you mean being able to call an openai compatible gateway from playground?

are you using our helm chart for deploying phoenix, could I see the configuration or pod definition

linking here for the storage increase request

Hi Seth D. the pricing page was pulled as we are planning on offering additional storage for free! For now its on a request basis so feel free to reach out if needed.

Justin L. im gonna approve your PR and then open up my new validators in a next one

Hi Justin L. I think the comments are great but im more so trying to protect installers who may not know whether they should mess with the securityContext's and how to properly set them, one idea and validator i wrote for example works under the following scenario

helm install phoenix . -f values.yaml --dry-run --set persistence.enabled=true --set postgresql.enabled=false --set securityContext.pod.enabled=true --set securityContext.pod.runAsUser=1000 --set securityContext.pod.fsGroup=1000 --set se
curityContext.pod.runAsGroup=1111

and returns warning

Error: INSTALLATION FAILED: execution error at (phoenix-helm/templates/phoenix/pvc.yaml:1:4): INFO: fsGroup (1000) differs from runAsGroup (1111). While this can work (fsGroup is added as supplementary group), consider aligning them for clarity. Set suppressMismatchedGroupWarning=true to acknowledge.

what are your thoughts on this pattern

Yes

I think instead we could add some validation that is persistance is on , we should stop deployment until the user also sets a working directory