quarkus-bot[bot]
commented
1 week ago :waning_crescent_moon: This workflow status is outdated as a new workflow run has been triggered.
Status for workflow Build (on pull request)
This is the status report for running Build (on pull request) on commit 41b40de598386145e5b0d436eec276582da2622b.
Failing Jobs
:warning: Artifacts of the workflow run were not available thus the report misses some details.
| Status | Name | Step | Failures | Logs | Raw logs |
|---|---|---|---|---|---|
| ✖ | Build and Test integration-tests on Java 17 | Run tests of integration-tests with JDK 17 |
:warning: Check → | Logs | Raw logs |
| ✖ | Build and Test integration-tests on Java 21 | Run tests of integration-tests with JDK 21 |
:warning: Check → | Logs | Raw logs |
| ✖ | Build and Test integration-tests on Java 23 | Run tests of integration-tests with JDK 23 |
:warning: Check → | Logs | Raw logs |
| ✖ | Native tests multiple-providers | Run integration tests multiple-providers |
:warning: Check → | Logs | Raw logs |
This PR shows how Azure OpenAI can be accessed with Azure Entra ID authorization code flow tokens.
The existing demo which shows how Vertex Gemini can be accessed with Google authorization code flow tokens has been refactored to show both Azure OpenAI and Vertex Gemini models with either Entra ID or Google access tokens.
@jmartisk @edeandrea @csotiriou, I'd appreciate your help with verifying the Entra ID plus Azure OpenAI combination (see README and I can help with configuring Azure OpenAI resource, deployment as well as Entra ID application).
Jan already verified the Vertex Gemini plus Google combo, but Jan, if you'd like please check it in this demo as well, you only need to update the redirect URI in the registered Google application.