Resource Group Name Validation Not Needed When Creating Publish Profiles.
See original GitHub issueThe deployment wizard warns the user that the resource group exists. However, the existence of it is not a problem at all.
When the user fills in the HostName
first and selects the subscription next, the wizard validates the input, and the deployment can proceed with no issues.
I suggest the validation be removed.
This will help with the confusion of having three different field descriptions as well. From what I can tell, Resource Group Name is the correct one.
This is on Bot Framework Composer v1.3.0. I hope it helps. Thanks.
Issue Analytics
- State:
- Created 3 years ago
- Comments:7 (7 by maintainers)
Top Results From Across the Web
Resource not found errors - Azure Resource Manager
Find the resource you're trying to use and examine the resource name, resource group, and subscription. Solution 2: Set dependencies. If you get ......
Read more >Azure App service cannot publish from visual studio 2019
Go to Get publish profile and save the profile locally. ... If the host name is not found, try the IP address instead...
Read more >Configuring Cataloging - Ex Libris Knowledge Center
Configure metadata profiles and authority vocabularies for bibliographic, holdings, and authority record operations in the MD Editor and for ...
Read more >How to Deploy using Publish Profile - FlexRule Resource Hub
Add the Area Name as ..\. ... Before you publish, you need to validate your package model. ... Deploy the Created Publish Profile...
Read more >Azure/naming/azurerm - Terraform Registry
This module helps you to keep consistency on your resources names for ... on naming currently on Microsoft docs are on the Not...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
@daronyondem Sure, Thank you.
Thanks @daronyondem, @luhan2017 will look at the PR and merge it if it gets accepted.