Is your feature request related to a problem? Please describe.
The DryRun switch is great to do some preliminary testing prior to actual deployment. However, it stops Publish-AdfV2FromJson short of the steps doing the actual deployment, so it's difficult to use a dry run to check the intended changes to the data factory.
Describe the solution you'd like
It would be great if DryRun didn't stop the deployment state but executed them in DryRun mode, only gathering the planned changes without executing them.
Describe alternatives you've considered
I can't think of any other way to implement this feature than via the DryRun switch.
Additional context
I'm thinking of a workflow similar to terraform plan, which does API calls to check the current state of the deployed objects agains the target state as per code to determine intended changes.
Is your feature request related to a problem? Please describe. The
DryRunswitch is great to do some preliminary testing prior to actual deployment. However, it stopsPublish-AdfV2FromJsonshort of the steps doing the actual deployment, so it's difficult to use a dry run to check the intended changes to the data factory.Describe the solution you'd like It would be great if
DryRundidn't stop the deployment state but executed them inDryRunmode, only gathering the planned changes without executing them.Describe alternatives you've considered I can't think of any other way to implement this feature than via the
DryRunswitch.Additional context I'm thinking of a workflow similar to
terraform plan, which does API calls to check the current state of the deployed objects agains the target state as per code to determine intended changes.