search

microsoft / Partner-Center-Storefront

A storefront that enables reseller partners to onboard customers and place orders for these customers.
MIT License
20 stars 55 forks source link

issue with deploying to azure #31

Open khaled6mmd opened 4 years ago

khaled6mmd commented 4 years ago

first of all the readme.md need to be updated as this part is different Build & Deploy on your own

Now I have tried to deploy through the deploy to azure button

I got this error 

Deployment to resource group 'new-test' failed.
Additional details from the underlying API that might be helpful: At least one resource deployment operation failed. Please list deployment operations for details. Please see https://aka.ms/DeployOperations for usage details.

tried to deploy with visual studio 2019 got the same thing following this article (which was out of date) https://docs.microsoft.com/en-us/archive/blogs/iwilliams/reseller-storefront

after the second attempt it built successfully (just did redeploy without any modifications)

but still got the default page with this text 

Hey, App Service developers!

Your app service is up and running.
Time to take the next step and deploy your code.

tried to publish by the publish option in visual studio

filled all the option Web.config

did not find any option that says secret key to fill publish succeeded, opened the site got the following message in the browser

[AdalServiceException: Response status code does not indicate success: 401 (Unauthorized).]
   Microsoft.Identity.Core.OAuth2.<GetResponseAsync>d__18`1.MoveNext() in D:\a\1\s\src\Microsoft.IdentityModel.Clients.ActiveDirectory\Core\OAuth2\OAuthClient.cs:66

[AdalServiceException: AADSTS7000215: Invalid client secret is provided.
Trace ID: 6c8d61c0-69fd-45b0-a796-6e20a4b83500
Correlation ID: bfd2304e-86f4-4b0d-b1d7-409c7a1db9aa
Timestamp: 2020-04-27 01:06:26Z]
toellbe commented 4 years ago

same here...

jasonwlindsay commented 4 years ago

I am also having the same issue. After deploying several times using the provided guide, I am still getting the default App Service page with no further details in Azure or the Kudu console. Doesn't work out of the gate despite multiple attempts. Is there any chance this will get updated to detail the azure storage account and/or key vaults? Not a huge fan of how these are generated automagically without the ability to control or override.

Euticus commented 3 years ago

Hi I am running into the same issue. Is there any way to debug further once I get to default App service page? Perhaps include resources to run this app locally first? That way I can ensure my keys are hitting the APIs to isolate the issues within Azure App service.