问题描述
我已经在Azure DevOps中创建了一个CD管道，该管道将通过ARM模板部署Azure自动化帐户和runbook，shedule，jobshedule.
I have created a CD pipeline in Azure DevOps that will deploy an Azure Automation account and a runbook , shedule , jobshedule through ARM templates.
除重新运行模板外，所有工作均正常.我的模板是仍在构建中的大型部署过程的一部分，因此在整个范围完成之前，用于创建运行手册，shedule，jobshedule的ARM模板将在每个发行版中重新运行.
All working fine except when rerunning the template. My template is a part of a large deployment process that is still under construction so until the total scope is finished the ARM template that creates the runbook, shedule, jobshedule will rerun with every release.
现在的问题如下:每当我使用新的发布管道重新运行模板时，都会收到以下错误消息
The problem right now is the following: Whenever I rerun the template with a new release pipeline, I receive following error
起初，我试图变得聪明，所以在我的工作台名称之前添加了一个GUI，但该工作台本身将运行手册与工作台连接在一起，并且部署足够聪明，可以确定该工作台已连接至该运行本.有没有一种方法可以使它仍然存在于DevOps思维定势/流程中，以便我可以毫无问题地重新运行模板.
At first I tried to be smart so added a GUI before the name of my jobshedule but the shedule itself attaches the runbook with the shedule and the deployment was smart enough to figure it out that the shedule was already connected to the runbook. Is there a way of making this still within the DevOps mindset / process so that I can rerun my templates with no problem.
我创建的atm变通办法是在每次部署时都删除操作表，但这似乎是一个非常糟糕的变通办法.
The workaround solution I have created atm is to delete the shedule at every deployment but that seems like a very bad workaround.
推荐答案
来自UserVoice/反馈论坛的相关功能请求为此处当前处于分类状态.
Related feature request from UserVoice / feedback forum is here that's currently in triaged state.
这篇关于重新运行自动化帐户，已经存在一个作业棚的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持！