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

Add metadata for spring.datasource.azure.passwordless-enabled #31976

Merged
merged 2 commits into from
Nov 14, 2022
Merged

Add metadata for spring.datasource.azure.passwordless-enabled #31976

merged 2 commits into from
Nov 14, 2022

Conversation

backwind1233
Copy link
Contributor

@backwind1233 backwind1233 commented Nov 7, 2022

metadata of spring.datasource.azure.passwordless-enabled can't be generated by spring-boot, we should add these metadata manully.

Follow-up issue #32124.

@ghost ghost added the azure-spring All azure-spring related issues label Nov 7, 2022
@backwind1233 backwind1233 self-assigned this Nov 7, 2022
@backwind1233 backwind1233 added Client This issue points to a problem in the data-plane of the library. feature-request This issue requires a new behavior in the product in order be resolved. labels Nov 7, 2022
@backwind1233 backwind1233 added this to the 2022-12 milestone Nov 7, 2022
@azure-sdk
Copy link
Collaborator

API change check

API changes are not detected in this pull request.

{
"name": "spring.datasource.azure.passwordless-enabled",
"type": "java.lang.Boolean",
"description": "Whether to enable supporting Azure identity token credentials.",
Copy link
Member

Choose a reason for hiding this comment

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

Suggested change
"description": "Whether to enable supporting Azure identity token credentials.",
"description": "Whether to enable passwordless connections to Azure databases by using Azure Active Directory token credentials.",

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Good point, I think we need to update our docs, codes as well.

Copy link
Member

Choose a reason for hiding this comment

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

Should we add OAuth2 before the token credentials

Copy link
Contributor Author

Choose a reason for hiding this comment

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

I hava updated this description to "Whether to enable passwordless connections to Azure databases by using OAuth2 Azure Active Directory token credentials." ,check here.

"name": "spring.datasource.azure.passwordless-enabled",
"type": "java.lang.Boolean",
"description": "Whether to enable supporting Azure identity token credentials.",
"sourceType": "com.azure.spring.cloud.service.implementation.passwordless.AzurePasswordlessProperties",
Copy link
Member

Choose a reason for hiding this comment

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

Do you think we can skip this sourceType here?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

If users can still jump to AzurePasswordlessProperties from IDE, then I think we can remove it.

Copy link
Member

Choose a reason for hiding this comment

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

But what can the users benefit from the jumping?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

But what can the users benefit from the jumping?

The point here is what's the expectation of users, I think by default users will have the expectation that it would be able to jump to a property class.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
azure-spring All azure-spring related issues Client This issue points to a problem in the data-plane of the library. feature-request This issue requires a new behavior in the product in order be resolved.
Projects
Status: Done
Development

Successfully merging this pull request may close these issues.

3 participants