SWA version: 2.0.6
Are you accessing the CLI from the default port :4280 ?
Make sure you are accessing the URL printed in the console when running swa start!
ℹ️ NOTE: Make sure to enable debug logs when running any swa commands using --verbose=silly
Describe the bug
I have 2 resource groups, both with a static web app having the same name. When I run the deploy command, specifying the output folder and the explicit resource group and app name, the website is always deployed to the same resource group.
To Reproduce
Steps to reproduce the behavior:
- Create resource group
a-rg
- Create static web app
same-name-swa within resource group a-rg
- Create resource group b-rg
- Create static web app
same-name-swa within resource group b-rg
- Run
swa deploy .out\ --resource-group b-rg --app-name same-name-swa
Actual behavior:
Website is deployed to static web app in resource group a-rg
Expect behavior:
Website is deployed to static web app in resource group b-rg
Desktop (please complete the following information):
SWA version: 2.0.6
Are you accessing the CLI from the default port
:4280?--port) and accessing the CLI from that port:4280ℹ️ NOTE: Make sure to enable debug logs when running any
swacommands using--verbose=sillyDescribe the bug
I have 2 resource groups, both with a static web app having the same name. When I run the deploy command, specifying the output folder and the explicit resource group and app name, the website is always deployed to the same resource group.
To Reproduce
Steps to reproduce the behavior:
a-rgsame-name-swawithin resource groupa-rgsame-name-swawithin resource groupb-rgswa deploy .out\ --resource-group b-rg --app-name same-name-swaActual behavior:
Website is deployed to static web app in resource group
a-rgExpect behavior:
Website is deployed to static web app in resource group
b-rgDesktop (please complete the following information):