Why are Stop-AdfTriggers and Start-AdfTriggers asymmetric?

[camilo-s]

Hi @NowinskiK, first of all thank you for the great library!!

Is there a reason why the two public functions Stop-AdfTriggers and Start-AdfTriggers are asymmetric in that the former receives strings FactoryName and ResourceGroupName as parameters, whereas the latter receives an ADF object?

As consequence of this, Stop-AdfTriggers can't receive a PublishOptions attribute, so the logic to selectively stop Triggers in Stop-Triggers doesn't come to effect.

[NowinskiK]

This is because:

• Stop-AdfTriggers is happening base on target ADF service, whereas
• Start-AdfTriggers uses code-ADF (just deployed) to identify which triggers should be started.
  Therefore, there is no reason to use PublishOptions in order to select triggers to be disabled.
  PublishOptions is reserved for publishing operation only.