部署插槽名称 [英] Deployment slot names

查看:74
本文介绍了部署插槽名称的处理方法,对大家解决问题具有一定的参考价值,需要的朋友们下面随着小编来一起学习吧!

问题描述

我创建了一个带有11个API应用程序的ASE,它们都共享相同的托管计划.  然后,我向每个应用程序添加了开发和部署插槽.  输入"dev"后,对于其中一个插槽名称,它是使用http://myapp-dev5e21 .....

I've created an ASE with 11 API Apps in it, they all share the same hosting plan.   I then added dev and deploy slots to each application.  After entering "dev" for one of the slot names, it gets created with http://myapp-dev5e21.....

Url和插槽名称添加了"5e21",的名字.  我意识到这些需求必须独特,但确实如此.  对于其他10个应用程序,它运行正常,只是其中一个导致了此问题.  如果我删除并重新创建广告位,则会更改为另一个 随机字符集..

The Url and slot name has added "5e21" to the name.   I realize these need to be unique, but they are.  It worked OK for the other 10 apps, its just one causing this problem.  If I delete and recreate the slot it changes to another random set of characters..

在私有ASE中,Url显然是唯一的.   UI甚至在更改之前就说确定".

The Url is obviously unique as its in a private ASE.  The UI even says it OK, before it changes it.

当Azure随机更改插槽名称时,很难遵守命名约定.

Hard to stick to naming conventions when Azure randomly changes the slot name.

有人看过吗?

尝试使用PowerShell创建插槽时也会发生同样的事情

The same thing happens trying to create the slot with PowerShell

New-AzureRmWebAppSlot-名称预测-ResourceGroupName CF-ASE-插槽开发

New-AzureRmWebAppSlot -Name forecast -ResourceGroupName CF-ASE -Slot dev

创建-> Forecast-dev0a9c ......

Creates -> forecast-dev0a9c......

推荐答案

原因是诸如myapp或Forecast-dev之类的网站已被其他人拥有,我们(有争议的)对名称实施唯一性全球范围.  我们将把反馈反馈给产品团队,看看是否可以更严格地执行.

The reason is the sites named like myapp or forecast-dev are already owned by others and we (debatable) enforce uniqueness on names globally.   we will give feed back to product team and see if the enforcement can be more granular.


这篇关于部署插槽名称的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持IT屋!

查看全文
登录 关闭
扫码关注1秒登录
发送“验证码”获取 | 15天全站免登陆