How can we help you today? How can we help you today?
rbigbie
Activity overview Badges (0) Posts (0) Comments (1)

Activity overview

Latest activity by rbigbie

Hi DanC, unfortunately it is not the Microsoft Data Client that caused the issue.  The issue arose once Red Gate released their September 23rd 2020 update: https://documentation.red-gate.com/sca/release-notes-and-other-versions/powershell-module-release-notes/sql-change-automation-powershell-4-3-release-notes 4.3.20267 - September 23, 2020 Features: Added ability to set Encrypt and TrustServerCertificate connection properties on New-DatabaseConnection  cmdlet Unfortunately the default Red Gate has chosen isn't working as before when no parameters are passed regarding this new "Feature". I would highly suggest that you make sure the default settings work when no parameters are passed so as to not break everyone else who isn't passing in parameters.  Unfortunately this broke out Azure DevOps deployment and now has our company not wanting to update the component in future releases. In the meantime we are passing as input params for the Azure Devops YAML Tasks: requiredVersionOfDlma: specific requiredVersion: 4.3.20259.22134 As far as calling PowerShell directly, we have one step that does that already because we are passing in parameters to the: # New-DatabaseReleaseArtifact # More Info: https://documentation.red-gate.com/display/SCA3/New-DatabaseReleaseArtifact $databaseReleaseArtifact = New-DatabaseReleaseArtifact -Source $buildDatabaseBuildArtifact -Target $databaseConnection -SqlCmdVariables $sqlcmdVariablesNewDatabaseReleaseArtifact Before this happens we call: $databaseConnection = New-DatabaseConnection -ServerInstance $env:SERVER_INSTANCE -Database $env:DATABASE -Username $env:USERNAME -Password $env:PASSWORD -TrustServerCertificate $true -Encrypt $false We had to add -TrustServerCertificate $true -Encrypt $false to make this work.  We didn't have to add those parameters before...hence the bad default settings on the SCA PowerShell modules you guys released. Please fix your default settings.  This is in a development environment in which we haven't had to worry about this before and now with your change it's something we have to deal with.  I consider it a breaking change that you released and not some minor feature that when releases doesn't break our process. Thank you for listening to our customer feedback. Also keep in mind that now we have to have a specific version because your Azure DevOps tasks defaults, won't work for us. As far as calling the PowerShell modules directly, we shouldn't have to do that because you released a "new" feature, and strip us away from using the Azure DevOps SCA tasks.  You can see how this causes us to not want to use or rely on the SCA Azure DevOps tasks.  The real solution here is to fix your default settings. It allows the feature to still be there, and not break people already consuming the SCA Azure DevOps tasks....... Thank you. / comments
  1. Community
  2. SQL Change Automation
  3. Latest version of Azure Build Task broken in Azure DevOps
Hi DanC, unfortunately it is not the Microsoft Data Client that caused the issue.  The issue arose once Red Gate released their September 23rd 2020 update: https://documentation.red-gate.com/sca/re...
0 votes
Total activity
2
Last activity
Member since
Following
0 users
Followed by
0 users
Votes
0
Subscriptions
1