Skip to content
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

e2e: update/fix extproc test #305

Conversation

alexagriffith
Copy link
Contributor

@alexagriffith alexagriffith commented Feb 6, 2025

Commit Message

make fixes to current test file

  • remove TEST_ in aws config name
  • skip if openai key is empty (this is for running locally for us, as we dont have that key)

Signed-off-by: Alexa Griffith <agriffith96@gmail.com>
Signed-off-by: Alexa Griffith <agriffith96@gmail.com>
@alexagriffith alexagriffith changed the title dont skip if openai key empty e2e: update/fix extproc test Feb 6, 2025
@alexagriffith alexagriffith marked this pull request as ready for review February 7, 2025 20:21
@alexagriffith alexagriffith requested a review from a team as a code owner February 7, 2025 20:21
Comment on lines +113 to +115
if tc.testCaseName == "openai" && openAIAPIKey == "" {
t.Skip("Skipping openai test case as TEST_OPENAI_API_KEY is not set")
}
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

please do not specialize openai. what happens when we are adding more providers? what about someone wanting to test openai but not aws? Can you simply add a env var requirement check and skip each case accordingly?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

what do you suggest? rn we skip all if no aws key, which makes sense, and we check openai key because its the only other one to check at the moment, if we add a new key we can check it too. can you help me understand better how it could be improved now? open to changing it

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

im not sure if an env var req check would look much different than this? maybe im not understanding

@mathetake
Copy link
Member

i went ahed and implemented the generic version in #326 - hope this works for you :)

@alexagriffith
Copy link
Contributor Author

I know it takes a little time, but I was def willing to update it just wanted to understand what it was you were suggesting. I understand the change though thanks!

@mathetake
Copy link
Member

yeah sorry i just wanted to fix it by myself as in hindsight i should've made it optional in the first place so i wanted to avoid wasting your time. Thanks for your help anyways!

daixiang0 pushed a commit to daixiang0/ai-gateway that referenced this pull request Feb 12, 2025
**Commit Message**

This makes each credential optional.

**Related Issues/PRs (if applicable)**

Closes envoyproxy#305

---------

Signed-off-by: Takeshi Yoneda <t.y.mathetake@gmail.com>
daixiang0 pushed a commit to daixiang0/ai-gateway that referenced this pull request Feb 12, 2025
**Commit Message**

This makes each credential optional.

**Related Issues/PRs (if applicable)**

Closes envoyproxy#305

---------

Signed-off-by: Takeshi Yoneda <t.y.mathetake@gmail.com>
daixiang0 pushed a commit to daixiang0/ai-gateway that referenced this pull request Feb 19, 2025
**Commit Message**

This makes each credential optional.

**Related Issues/PRs (if applicable)**

Closes envoyproxy#305

---------

Signed-off-by: Takeshi Yoneda <t.y.mathetake@gmail.com>
Signed-off-by: Loong <long0dai@foxmail.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants