-
Notifications
You must be signed in to change notification settings - Fork 67
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
Trigger Activation Failure Post-Selective Deployment #386
Comments
Are you sure that the trigger is NOT Started after the deployment?
|
Thank you for your quick answer! Yes, I am certain these triggers stays "Stopped" deployment regardless of the runtimeState value in the JSON definition trigger file, at least with the presented above parameters. I have double checked the post-deployment status in the portal and also using the PowerShell command you suggested. |
It must be some specific scenario in your case because this is a very common pattern to deploy and start a trigger. |
At the moment I can only share the script below unfortunately:
A trigger json definition can be as the one described in the previous comment. I believe a critical factor that might be contributing to this problem is the parameter $opt.TriggerStopMethod being set to "DeployableOnly" - but for a selective deployment this value is desired. Here is a very similar lead but in this case trigger is defined as already deployed (second run): |
Hi @NowinskiK - will you be able to help with this issue? |
I have limited capacity atm, but I will take a look at this as soon as I can. |
Thank you very much! Your assistance would be greatly appreciated! |
This only happens when |
Describe the bug
Hi Kamil!
We are using the PowerShell module for our selective ADF objects deployments, and it works great (ADF as a resource pre-exists). Basically, we defined our PowerShell script to explicitly include the desired objects to be deployed from our repository. During deployment, the only caveat is that after the first deployment (creation) of each trigger, it stays disabled, even though in the trigger JSON definition it is declared as
Started
(desired state). I am attaching the parameters set for a deployment below.The described case is "S01" from your matrix-of-behavior-logic-1.
Parameters the script has been run with:
To Reproduce
Generate a PowerShell script with parameters mirroring the ones provided above. Execute the script to initiate a selective deployment.
Expected behavior
Trigger is active after first selective deployment.
Version of PowerShell module of:
azure.datafactory.tools 1.8.0
Logs
The deployment log erroneously indicates that the trigger has already started, despite it not being active in reality.
Trigger definition
The text was updated successfully, but these errors were encountered: