-
Notifications
You must be signed in to change notification settings - Fork 2k
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
Delete un-supported AAD features. #23895
Delete un-supported AAD features. #23895
Conversation
…ilter, because they are deprecated and will not supported any more in version 4.0.
…hClient. And related test files.
is this PR finished? |
@stliu , If the reviewer think current commits is OK to merge, I'll merge it. |
but how to say "OK" safely with incompletable information? |
I can only see you deleted something in a commit, if that's the completed information, then of course I'd say no, why delete those files? don't we need them anymore? |
Yes, we don't need them any more. |
This feature is deprecated in version 3.x. We will not support these features in 4.0.0. I found the first PR of this feature: microsoft/azure-spring-boot#97 It's on 2017-08-07. At that time, there is no spring-security-oauth2-resource-server. spring-security-oauth2-resource-server first released on 2018-09-21. refs: https://repo1.maven.org/maven2/org/springframework/security/spring-security-oauth2-resource-server/
if so, wouldn't it be more appreciated to have separated PR for each task instead of all grouped into this general "implement azure spring security 4.0"? for example, this removes some feature, I think it deserves its own github issue with detailed info of :
|
If I do like that, then PR2 depends on PR1, and PR3 depends on PR 2, etc.. So I prefer to use one PR.
My current plan is write doc after coding work finished. |
NO, pull request is not working like what your describe. One PR should do one specific change, having a corresponding issues link to it you can't use one PR to do all the works, that would make things untrackable. |
…e changelogs will be deleted in version 4.0.
This pull request is protected by Check Enforcer. What is Check Enforcer?Check Enforcer helps ensure all pull requests are covered by at least one check-run (typically an Azure Pipeline). When all check-runs associated with this pull request pass then Check Enforcer itself will pass. Why am I getting this message?You are getting this message because Check Enforcer did not detect any check-runs being associated with this pull request within five minutes. This may indicate that your pull request is not covered by any pipelines and so Check Enforcer is correctly blocking the pull request being merged. What should I do now?If the check-enforcer check-run is not passing and all other check-runs associated with this PR are passing (excluding license-cla) then you could try telling Check Enforcer to evaluate your pull request again. You can do this by adding a comment to this pull request as follows: What if I am onboarding a new service?Often, new services do not have validation pipelines associated with them, in order to bootstrap pipelines for a new service, you can issue the following command as a pull request comment: |
/azp run java - spring - ci |
Azure Pipelines successfully started running 1 pipeline(s). |
Hi, @stliu . Hi, @saragluna , @zhichengliu12581 . |
Fixed double header issue (Azure#23895)
Resolve #23922