-
Notifications
You must be signed in to change notification settings - Fork 586
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
PowerShell Script produced by azure-data-factory-utilities doesn't account for parameterised runtime state of triggers #387
Comments
Which azure-data-factory-utilities package are you using? Please share the location of the package. |
***@***.***/azure-data-factory-utilities
This npm package as described here
https://docs.microsoft.com/en-gb/azure/data-factory/continuous-integration-delivery-improvements#continuous-deployment-improvements
…On Wed, 25 May 2022, 6:56 pm Hao-Microsoft, ***@***.***> wrote:
Which azure-data-factory-utilities package are you using? Please share the
location of the package.
—
Reply to this email directly, view it on GitHub
<#387 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AB63SL3ILNMTAYOR6CUH4E3VLZSUDANCNFSM5WIJIURA>
.
You are receiving this because you authored the thread.Message ID:
***@***.***>
|
@microsoft/azure-data-factory-utilities This npm package as described here |
I'm facing the same issue. @Hao-Microsoft the script should be updated to take parameters into account |
@crystalgeek and @dsfrederic , we are aware of this issue and will be working on the fix. |
In PR #433 I've provided a fix |
Awesome thank you @dsfrederic ! It looks like you are already using the newer/better scripts. We'll fix this issue for both. |
The issue has been fixed now in both places - in this repository (PrePostDeploymentScript.Ver2.ps1), and in npm package (version 1.0.0). If you are using NPM package, the fix is available only in the latest version and should use build-preview command as: |
I am having a problem with the recommended CI/CD for ADF. Using the azure-data-factory-utilities package.
When ADF trigger runtimestate is included in the arm-template-parameters-definition.json file
"Microsoft.DataFactory/factories/triggers": { "properties": { "runtimeState": "=",
This produces an ARMTemplate which adds parameters to the runtimeState property ARMTemplateForFactory.json
{ "name": "[concat(parameters('factoryName'), '/BlobTrigger')]", "type": "Microsoft.DataFactory/factories/triggers", "apiVersion": "2018-06-01", "properties": { "annotations": [], "runtimeState": "[parameters('BlobTrigger_properties_runtimeState')]",
The powershell script for Pre/Post Deployment PrePostDeploymentScript.ps1 is expecting the runtimeState to be "Started" when defining triggers to start. This means that if parameterised these triggers don't get started even if they were previously
$triggersToStart = $triggersInTemplate | Where-Object { $_.properties.runtimeState -eq "Started" -and ($_.properties.pipelines.Count -gt 0 -or $_.properties.pipeline.pipelineReference -ne $null)} | ForEach-Object { New-Object PSObject -Property @{
The text was updated successfully, but these errors were encountered: