You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When updating our solutions packags we noticed that dbup-sqlserver has a dependency to Microsoft.Azure.Services.AppAuthentication >= 1.6.2 which is deprecated. Suggesting an alternate implementation with regards to the suggestion in issue DbUp/DbUp#641.
Nice. We currently don't even use sql server with Azure so if it could be opted in it would be great. Minimum the migration to Azure.Identity would be much appreciated.
I used GetTokenAsync since thats what was used with the current build. If that needs to be changed for this PR to be accepted, someone please let me know and I change it.
Good catch, I'll fix this. I was going to let environment variables handle these settings, but since tenantId is already a param of the constructor, I agree its better to use that.
I believe this has been removed, but additional parameters like that can be specified using environment variables, see the README here: https://www.nuget.org/packages/Azure.Identity
@peymanr34@ernstad@mjauernig@droyad
I have resubmitted a PR with the new repo setup to resolve this issue with the suggestions above, please review and approve/comment.
dbup-sqlserver depends on Microsoft.Azure.Services.AppAuthentication 1.6.2,
which depends on Microsoft.IdentityModel.Clients.ActiveDirectory 5.2.9,
which depends on a bunch of mostly deprecated packages:
Activity
mjauernig commentedon Aug 16, 2023
Is a special Azure Implementation necessary? Or would you use Azure with the dbup-sqlserver module and this Azure Connection Settings?
mjauernig commentedon Aug 16, 2023
Found a migration guide. I will take a look in the next days.
ernstad commentedon Aug 17, 2023
Nice. We currently don't even use sql server with Azure so if it could be opted in it would be great. Minimum the migration to
Azure.Identitywould be much appreciated.evochriso commentedon Nov 27, 2023
@mjauernig the linked PR should resolve this issue, can you review? Thanks!
ernstad commentedon Jan 15, 2024
Any update on the PR?
peymanr34 commentedon Jan 31, 2024
The linked PR has some issues:
GetTokenmethod which I think it should be used instead ofGetTokenAsync.tenantIdparameter hasn't been used, it should've been passed to theTokenRequestContext.azureAdInstanceparameter hasn't been used (which I don't know where it should go, maybe it's redundant?).evochriso commentedon Jan 31, 2024
@peymanr34 @ernstad @mjauernig :
evochriso commentedon Feb 12, 2024
@peymanr34 @ernstad @mjauernig @droyad
I have resubmitted a PR with the new repo setup to resolve this issue with the suggestions above, please review and approve/comment.
Bartleby2718 commentedon Feb 12, 2024
Looking very much forward to this being reviewed!
dbup-sqlserverdepends onMicrosoft.Azure.Services.AppAuthentication1.6.2,which depends on
Microsoft.IdentityModel.Clients.ActiveDirectory5.2.9,which depends on a bunch of mostly deprecated packages:
Bartleby2718 commentedon Feb 12, 2024
Unrelated, but I noticed in @evochriso's PR that
dbup-sqlserverdoesn't have a corresponding nuspec file. Is this intentional?evochriso commentedon Feb 12, 2024
This is intentional - the nuspec file gets generated by the build pipeline.
ernstad commentedon Apr 26, 2024
Any update on the issue and linked PR?