Movatterモバイル変換


[0]ホーム

URL:


Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

Sign up
Appearance settings

Proxy registry integration for GraphQL clients#51286

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 ourterms of service andprivacy statement. We’ll occasionally send you account related emails.

Already on GitHub?Sign in to your account

Open
jmartisk wants to merge1 commit intoquarkusio:main
base:main
Choose a base branch
Loading
fromjmartisk:graphql-client-proxy-registry

Conversation

@jmartisk
Copy link
Contributor

No description provided.

@quarkus-bot
Copy link

Thanks for your pull request!

Your pull request does not follow our editorial rules. Could you have a look?

  • description should not be empty, describe your intent or provide links to the issues this PR is fixing (usingFixes #NNNNN) or changelogs

This message is automatically generated by a bot.

@quarkus-bot

This comment has been minimized.

@jmartiskjmartiskforce-pushed thegraphql-client-proxy-registry branch from737174e to185ff61CompareNovember 28, 2025 11:14
// use the proxy configuration registry
resolveProxyConfiguration(quarkusConfig)
.ifPresent(proxyConfiguration -> {
transformed.setProxyHost(proxyConfiguration.host());
Copy link
ContributorAuthor

Choose a reason for hiding this comment

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

Yes, some properties of the proxy configuration aren't supported on the SmallRye side yet, so they are ignored. I will fix that later too, but it will need a SmallRye-side change

ppalaga reacted with thumbs up emoji
Copy link
Contributor

Choose a reason for hiding this comment

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

Alternatively, we could document somewhere which options are supported in this extension.

You could also warn on the console if unsupported optional settings are present.

Copy link
ContributorAuthor

Choose a reason for hiding this comment

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

Ok I've added a warning ifnon-proxy-hosts is set and an error iftype != http

@quarkus-bot

This comment has been minimized.

@quarkus-bot

This comment has been minimized.

@github-actions
Copy link

github-actionsbot commentedNov 28, 2025
edited
Loading

🎊 PR Previewd2bb1ce has been successfully built and deployed tohttps://quarkus-pr-main-51286-preview.surge.sh/version/main/guides/

  • Images of blog posts older than 3 months are not available.
  • Newsletters older than 3 months are not available.

Copy link
Contributor

@ppalagappalaga left a comment

Choose a reason for hiding this comment

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

Looks great, thanks@jmartisk!

// use the proxy configuration registry
resolveProxyConfiguration(quarkusConfig)
.ifPresent(proxyConfiguration -> {
transformed.setProxyHost(proxyConfiguration.host());
Copy link
Contributor

Choose a reason for hiding this comment

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

Alternatively, we could document somewhere which options are supported in this extension.

You could also warn on the console if unsupported optional settings are present.

@jmartiskjmartiskforce-pushed thegraphql-client-proxy-registry branch from185ff61 to43bb59fCompareNovember 28, 2025 12:09
@quarkus-bot
Copy link

quarkus-botbot commentedNov 28, 2025
edited by github-actionsbot
Loading

Status for workflowQuarkus CI

This is the status report for runningQuarkus CI on commit43bb59f.

✅ The latest workflow run for the pull request has completed successfully.

It should be safe to merge provided you have a look at the other checks in the summary.

Warning

There are other workflow runs running, you probably need to wait for their status before merging.

You can consult theDevelocity build scans.

@quarkus-bot
Copy link

Status for workflowQuarkus Documentation CI

This is the status report for runningQuarkus Documentation CI on commit43bb59f.

✅ The latest workflow run for the pull request has completed successfully.

It should be safe to merge provided you have a look at the other checks in the summary.

});
if (proxyConfiguration.type() !=ProxyType.HTTP) {
thrownewConfigurationException(
"Only HTTP proxy type is supported by the GraphQL client extension at the moment.");
Copy link
Contributor

Choose a reason for hiding this comment

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

Would it be clear from the stack trace or elsewhere, which specific config key is incompatible with this extension? We could perhaps also suggest some corrective action. How about

"Quarkus SmallRye GraphQL extension currently supports only proxy type 'HTTP'. You may either change the value of 'quarkus.proxy"+ (quarkusConfig.proxyConfigurationName().isEmpty() ? "" : ("." + quarkusConfig.proxyConfigurationName().get)) +".type' to 'HTTP', or you can create a new proxy configuration having 'quarkus.proxy.\"some-name\".type = HTTP' and set 'quarkus.graphql.proxy-configuration-name = some-name'.

Copy link
Contributor

Choose a reason for hiding this comment

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

Similarly, the config key could be named also in the above Non-proxy hosts message.

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

Reviewers

@phillip-krugerphillip-krugerAwaiting requested review from phillip-kruger

1 more reviewer

@ppalagappalagappalaga approved these changes

Reviewers whose approvals may not affect merge requirements

At least 1 approving review is required to merge this pull request.

Assignees

No one assigned

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

2 participants

@jmartisk@ppalaga

[8]ページ先頭

©2009-2025 Movatter.jp