-
Notifications
You must be signed in to change notification settings - Fork 910
Add graalvm reachability metadata to sso service #5840
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
Comments
@gbaso Sorry for the long delay in replying. Taking a look at the PR. |
@debora-ito not related to the OP PR, but he mentions that sso oidc reachability was done long ago. The issue is that the referenced class |
@scrocquesel good catch 🤦🏻♀️ thank you! @gbaso would you mind fixing ssooidc/reflect-config.json in your PR? |
@debora-ito sure, I'll fix it now. |
I have fixed this issue with GraalVM substitution in the Quarkus extension and we faced another issue. Both providers make use of a static field which is statically initialized with a call to userHomeDirectory(). |
Describe the feature
Add reachability metadata for service
sso
, namely for the constructor ofSsoProfileCredentialsProviderFactory
.Use Case
GraalVM native image requires reflection hints for code that is only used by reflection.
Proposed Solution
Add a file
reflect-config.json
undersrc/main/resources/META-INF/native-image/software.amazon.awssdk/sso
with:Other Information
Native hints can be provided by the application (e.g., for spring applications, via
@ImportRuntimeHints
), but it's mostly a try-and-error process. Libraries providing metadata simplify the operation of building a native image considerably.Other aws services already provide metadata, see ssooidc.
Acknowledgements
AWS Java SDK version used
2.29.52
JDK version used
21.0.5
Operating System and version
MacOS 15.2
The text was updated successfully, but these errors were encountered: