Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Cannot specify resource group without also using deployment slots #5984

Closed
CarsonTolleshaug opened this issue Dec 6, 2017 · 2 comments
Closed
Assignees
Labels
Area: AzureAppService Label to monitor Azure App Service issues Area: Release enhancement

Comments

@CarsonTolleshaug
Copy link

CarsonTolleshaug commented Dec 6, 2017

The "Azure App Service Deploy" task does not allow the user to specify the resource group of the app unless "Deploy to slot" is checked.

I have two app services which have the same name, but are in two separate resource groups on the same subscription. As far as I can tell, there is currently no way for me to use the Azure App Service Deploy task to deploy code to both services, meaning I will have to resort to using a custom powershell task or other hack-ish solution.

For what it's worth, the app services are in two separate ASEs as well.

Am I missing something? If not can you please consider changing the task/UI to allow for this?

Thanks,
Carson

@vincent1173
Copy link
Contributor

@CarsonTolleshaug , thanks for reporting the issue.
Can you try selecting the required resource group and type slot as "production" as a workaround?

Will update the thread on the latest info, if any.

@CarsonTolleshaug
Copy link
Author

Thanks Vincent, yes that works. We ended up just using deployment slot anyway though which solved our issue.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Area: AzureAppService Label to monitor Azure App Service issues Area: Release enhancement
Projects
None yet
Development

No branches or pull requests

4 participants