-
Notifications
You must be signed in to change notification settings - Fork 10.3k
Remove obsolete AzureAd #27955
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
Remove obsolete AzureAd #27955
Conversation
There's a lot of discussion on #27529 about if removing these APIs is actually necessary. Yes they've been replaced, but the old ones still work so do we need to forcibly break people that are still using them? Is there a clear functional problem here driving the removal? |
These have been a constant source of issues and errors, doesn't an LTS seem like a good time to encourage them to move to the intended final destination? Basically bullet 2
|
This seems analogous to our Azure Key Vault configuration provider which we also dropped rather than keeping around with obsolete since its an externally owned feature |
We already moved the templates so that should cut down on the incoming issues. The main concern is if we're forcing change on people who weren't broken. That's @blowdart's call. |
Right, I checked with @blowdart before opening the PR :) |
I lean on kill it off, obviously. People do need to change, because the v1 endpoint will retire, probably before the LTS expiry. Same with the app creation API. |
This apparently needs a wider discussion :) |
/azp run |
Azure Pipelines successfully started running 2 pipeline(s). |
@blowdart did we get everything straightened out on the process side on your end for approval? |
We did not. The thread is ongoing. I'll ressurect it. We may have to keep it for a while longer. |
Closing until v7 |
Part of #27529