-
Notifications
You must be signed in to change notification settings - Fork 18
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Kent/agora 2553 spike an orchestrator testing pattern #554
base: main
Are you sure you want to change the base?
Conversation
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
694433c
to
930afe9
Compare
export function setEnv(envConfig: { [key: string]: string }) { | ||
Object.keys(envConfig).forEach((key) => { | ||
process.env[key] = envConfig[key]; | ||
}); | ||
} |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Is this being called somewhere? What is invoking this? I don't see it.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
FWIW, I'm not asking because I'm worried about about dead code. I'm asking, because a key part of this is how we're managing the sets of environment variables in the orchestrator.
|
||
// Main loop for test runner | ||
async function main() { | ||
const config: Config = loadConfig() as Config; |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I would have expected a tenant-config.yaml
to load a single tenant's configuration. Not a set of tenants.
The orchestrator could optionally take a list, and loop over each of them.
No description provided.