Skip to content

Conversation

@github-actions
Copy link
Contributor

@github-actions github-actions bot commented Jun 5, 2025

Backport: #1163

Note: CI is not automatically triggered on backported PRs, please comment 'ok to test' to launch Jenkins jobs

Many thanks for submitting your Pull Request ❤️!

Fix #1156.

Additionally, now OAuth2 provider also has an injected CredentialsProvider.

Please make sure that your PR meets the following requirements:

  • You have read the contributors guide
  • Your code is properly formatted according to our code style
  • Pull Request title contains the target branch if not targeting main: [0.9.x] Subject
  • Pull Request contains link to the issue
  • Pull Request contains link to any dependent or related Pull Request
  • Pull Request contains description of the issue
  • Pull Request does not include fixes for issues other than the main ticket
How to backport a pull request to a different branch?

In order to automatically create a backporting pull request please add one or more labels having the following format backport-<branch-name>, where <branch-name> is the name of the branch where the pull request must be backported to (e.g., backport-quarkus2 to backport the original PR to the quarkus2 branch).

NOTE: backporting is an action aiming to move a change (usually a commit) from a branch (usually the main one) to another one, which is generally referring to a still maintained release branch. Keeping it simple: it is about to move a specific change or a set of them from one branch to another.

Once the original pull request is successfully merged, the automated action will create one backporting pull request per each label (with the previous format) that has been added.

If something goes wrong, the author will be notified and at this point a manual backporting is needed.

NOTE: this automated backporting is triggered whenever a pull request on main branch is labeled or closed, but both conditions must be satisfied to get the new PR created.

…1163)

* Fix #1156 - Move AuthProviders SyntheticBean generation to Runtime

Signed-off-by: Ricardo Zanini <[email protected]>

* Add a meaningful log message to IT

Signed-off-by: Ricardo Zanini <[email protected]>

* Update client/integration-tests/override-credential-provider/src/test/java/io/quarkiverse/openapi/generator/it/creds/CustomCredentialsProviderTest.java

Co-authored-by: Gonzalo Muñoz <[email protected]>

---------

Signed-off-by: Ricardo Zanini <[email protected]>
Co-authored-by: Gonzalo Muñoz <[email protected]>
@hbelmiro
Copy link
Contributor

@ricardozanini the CI is red.
Can you please take a look?
It seems to be just the non-lts version being referenced here: https://github.com/quarkiverse/quarkus-openapi-generator/pull/1172/files#diff-3ad2f9bc7c592d72973fc3b1a2dc26b909f86d3a79501b22c8c8f9fbc99cb9f7R9

Signed-off-by: Ricardo Zanini <[email protected]>
@github-actions
Copy link
Contributor Author

🎊 PR Preview 9d7eb5a has been successfully built and deployed. See the documentation preview: https://quarkus-openapi-generator-preview-pr-1172.surge.sh

@ricardozanini ricardozanini merged commit 0b38a70 into main-lts Jun 11, 2025
11 checks passed
@ricardozanini ricardozanini deleted the main-lts_issue-1156-2 branch June 11, 2025 15:19
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants