Deploy only Triggers - with no other dependencies #197
-
We are trying to deploy just the Triggers, without the dependencies (Pipeline etc) as part of a release branch. The extension is still looking for the referenced object, which are not part of this utility release branch. Is there an option to bypass this check ? Thank you |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment 3 replies
-
First of all - build pipeline should wrap up all objects of a given ADF as artifact. So, even when you're making selective deployment (triggers only) - all other objects should be available there. Example:
|
Beta Was this translation helpful? Give feedback.
First of all - build pipeline should wrap up all objects of a given ADF as artifact. So, even when you're making selective deployment (triggers only) - all other objects should be available there.
However, in some specific scenarios (perhaps like yours) there is an option that allows you to skip reference validation:
IgnoreLackOfReferencedObject
It's available among the other publish options in the PowerShell module (just noticed it must be documented)
Example: