You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi, I am including the linked services as part of CI pipeline using you Azure Data Factory deployment task and it is working well.
On the first pipeline un/release it creates the linked services in a new data factory which is great but the linked services in the target data factory use different resources with different credentials so if I update these in the target, they are then replaced to the source data factory settings when the pipeline next runs.
I don't see a way to handle this in the deployment task but it would be a neat feature to not reset these. As for the pipelines and datasets it's less of an issue.
Or is there a different way to handle this besides just removing the linked services deployment from the pipeline for any subsequent builds/runs?
thanks
The text was updated successfully, but these errors were encountered:
Thanks for your feedback and indeed the default behavior is to overwrite all content. And there is no option to alter that, but it is a good enhancement to only deploy new artifacts.
Hi, I am including the linked services as part of CI pipeline using you Azure Data Factory deployment task and it is working well.
On the first pipeline un/release it creates the linked services in a new data factory which is great but the linked services in the target data factory use different resources with different credentials so if I update these in the target, they are then replaced to the source data factory settings when the pipeline next runs.
I don't see a way to handle this in the deployment task but it would be a neat feature to not reset these. As for the pipelines and datasets it's less of an issue.
Or is there a different way to handle this besides just removing the linked services deployment from the pipeline for any subsequent builds/runs?
thanks
The text was updated successfully, but these errors were encountered: