Trigger not started after deployment (case B02)

[TybulOnAzure]

Hi @NowinskiK

I'm having some issues with starting a trigger. Let me describe my case:

1. I use 1.7.000 version of azure.datafactory.tools.

2. I have a simple CI/CD pipeline that deploys ADF using selective approach. One of objects selected for deployment is my trigger (FINES_AND_FEES_MW_US_TRIGGER).

3. Publish options are as follows:
   

4. Current state of FINES_AND_FEES_MW_US_TRIGGER trigger is as follows:

   • Started - in code repository,
   • Stopped - in ADF live service.

5. So I guess it falls under B02 case from your table:
   

6. During Stopping triggers... step, FINES_AND_FEES_MW_US_TRIGGER trigger is not stopped as it was already stopped in target ADF service - that is fine:
   

7. Then, during Deployment of all ADF objects... step, this trigger is deployed - that is fine:
   

8. However, during Starting triggers... step, it is not started as adf.tools believes that it is already started which is not true:
   

9. As a result, the trigger is in Stopped state in target ADF service, which is against B02 case.

Could you please take a look at it and let me know if my understanding is correct?

I might be wrong but I think that the issue might be in https://github.com/Azure-Player/azure.datafactory.tools/blob/master/private/Start-Triggers.ps1 file:

as maybe the code checks for disabled triggers in the JSON code instead of live ADF service.

Piotr

[TybulOnAzure]

On the other hand, B01 case works just fine (using the same CI/CD pipeline):

1. The current state and desired state are set to Started, all other options are the same as previously.

2. Stopping triggers:
   

3. Starting triggers:
   

[chalabaj]

Had similar issue once there was timeout during trigger deployment. Next redeployment showed that the trigger is already started, but in ADF live mode trigger was stopped.

[NowinskiK]

Thanks @TybulOnAzure & @chalabaj for details. I found the bug and finally had some time to fix it (during the flight to MVPSummit).
Follow this ticket: #386

[NowinskiK]

Guys, @TybulOnAzure & @chalabaj - this issue is fixed now and released in 1.10.0-preview.
Thanks for your patience! Please test the new version before public release.

[chalabaj]

Hi, I would like to but I cant until #374 is fixed as well. Anyway. Thanks for this fix.

[NowinskiK]

@chalabaj #374 is a public preview now - no excuses against testing :)