Skip to content

Decide + wire how the staging gateway gets the Azure endpoint + key #37

Description

@Kenny-Heitritter

Question

There is no automated path today from Azure terraform outputs (ai_foundry_endpoint, primary key) to the gateway's runtime env. Decide the mechanism — k8s secret / GCP Secret Manager / managed env on the staging qbraid-account deployment — and wire it so the staging gateway can reach qbraid-staging-ai-services with AZURE_OPENAI_ENDPOINT / AZURE_OPENAI_API_KEY.

This is the "hook it up to our pipeline for staging usage" question. Decision-led (HITL — depends on qBraid's secret-management conventions), then a small wiring task. Needs the staging Azure account to exist first (real endpoint/key to plumb).

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    wayfinder:grillingWayfinder ticket: HITL grilling decision

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions