简体   繁体   English

如何自动化 Azure 数据工厂管道部署

[英]How to automate Azure data factory pipeline deployments

I want to automate Azure data factory pipeline deployments.我想自动化 Azure 数据工厂管道部署。 I have Self Hosted Integration runtimes with a different name in each environment (ie SHIR-{environment}).我在每个环境中都有不同名称的自托管集成运行时(即 SHIR-{environment})。 I have different data sources and destinations for each environment.对于每个环境,我都有不同的数据源和目的地。 (ie different SQL server names or Hostnames) How can I perform the automatic weekly deployments to promote changes from GitHub dev branch to stage and stage to production? (即不同的 SQL 服务器名称或主机名)我如何执行自动每周部署以促进从 GitHub 开发分支到阶段和阶段到生产的更改? I don't want to modify these database server names in linked services during the GitHub PR merge.我不想在 GitHub PR 合并期间修改链接服务中的这些数据库服务器名称。

To set up automated deployment, start with an automation tool, such as Azure DevOps.要设置自动化部署,请从自动化工具开始,例如 Azure DevOps。 Azure DevOps provides various interfaces and tools in order to automate the entire process. Azure DevOps 提供各种接口和工具,以实现整个过程的自动化。

  1. A development data factory is created and configured with Azure Repos Git. All developers should have permission to author Data Factory resources like pipelines and datasets.使用 Azure Repos Git 创建和配置开发数据工厂。所有开发人员都应有权创作数据工厂资源,如管道和数据集。
  2. A developer creates a feature branch to make a change.开发人员创建功能分支以进行更改。 They debug their pipeline runs with their most recent changes.他们使用最近的更改调试管道运行。 For more information on how to debug a pipeline run, see Iterative development and debugging with Azure Data Factory.有关如何调试管道运行的更多信息,请参阅使用 Azure 数据工厂进行迭代开发和调试。
  3. After a developer is satisfied with their changes, they create a pull request from their feature branch to the main or collaboration branch to get their changes reviewed by peers.在开发人员对他们的更改感到满意后,他们会创建从其功能分支到主要或协作分支的拉取请求,以使他们的更改得到同行的审查。
  4. After a pull request is approved and changes are merged in the main branch, the changes get published to the development factory.在 pull request 被批准并在主分支中合并更改后,更改将发布到开发工厂。
  5. When the team is ready to deploy the changes to a test or UAT (User Acceptance Testing) factory, the team goes to their Azure Pipelines release and deploys the desired version of the development factory to UAT.当团队准备好将更改部署到测试或 UAT(用户验收测试)工厂时,团队会转到其 Azure 管道版本并将开发工厂的所需版本部署到 UAT。 This deployment takes place as part of an Azure Pipelines task and uses Resource Manager template parameters to apply the appropriate configuration.此部署作为 Azure 管道任务的一部分进行,并使用资源管理器模板参数来应用适当的配置。
  6. After the changes have been verified in the test factory, deploy to the production factory by using the next task of the pipelines release.在测试工厂验证更改后,使用管道发布的下一个任务部署到生产工厂。

For more information follow this link有关更多信息,请点击此链接

声明:本站的技术帖子网页,遵循CC BY-SA 4.0协议,如果您需要转载,请注明本站网址或者原文地址。任何问题请咨询:yoyou2525@163.com.

 
粤ICP备18138465号  © 2020-2024 STACKOOM.COM