mspnp / AzureNamingTool

The Azure Naming Tool is a .NET 8 Blazor application, with a RESTful API. The UI consists of several pages to allow the configuration and generation of Azure Resource names. The API provides a programmatic interface for the functionality.
https://aka.ms/azurenamingtool
MIT License
346 stars 721 forks source link

Deployed 4.1.0 and just getting default Azure App Service page. #94

Closed epfaffinger closed 6 months ago

epfaffinger commented 6 months ago

I just deployed version 4.1.0 to a new app service and the workflow task completed successfully but all that is displayed is the default Azure app service page indicating "your app is running and waiting for content?

I deployed 4.0.1 using the same install process with no issue? Let me know if you need any logs. I've deleted the app services and followed the install for "Run as an Azure Web App Using GitHub Action" again resulting in the same issue.

epfaffinger commented 6 months ago

Just tried updating an existing working app service running 4.0.1 and it now just shows the default Azure app service page as well, the naming tool is gone? Is there a way to revert?

epfaffinger commented 6 months ago

Is there a way to push v 4.0.1, I am dead in the water here?

BryanSoltis commented 6 months ago

Hi @epfaffinger,

Thank you for your feedback, but sorry to hear you're having issues. We haven't recieved any reports of any trouble deploying, so I am curious as to why yours is not working.

For v4.1.0:

image

For v4.0.1:

https://learn.microsoft.com/en-us/visualstudio/deployment/deploying-applications-services-and-components-resources?view=vs-2022#azure

Hope this helps. Let me know if you find anything in your logs/findings and I'll if I can figure out why yours is failing.

epfaffinger commented 6 months ago

Hi @Bryan @.***>,

Thanks so much for the quick reply. I am not a developer but an Azure Admin so I am fairly new with Git/GitHub so I really appreciate your help (and patience 😊 ).

  1. I have tried restarting the app service and have deployed fresh multiple times with the same results.
  2. Below is a screen shot of the files:

[A screenshot of a computer Description automatically generated]

[A screenshot of a computer Description automatically generated] [A screenshot of a computer Description automatically generated] [A screenshot of a computer Description automatically generated] [A screenshot of a computer Description automatically generated] [A screenshot of a computer Description automatically generated]

When I try to view the log stream it just sits forever at “Connecting” so can’t see any more info there. If there are any specific logs that would be helpful please let me know and I will gather them.

From an Azure perspective the deployment logs just show success, from GitHub I do have 15 warnings which I assumed were ok?

Annotations 15 warnings check-secretshttps://github.com/epfaffinger/AzureNamingTool/actions/runs/8298362409/job/22711563000 Node.js 16 actions are deprecated. Please update the following actions to use Node.js 20: @. For more information see: https://github.blog/changelog/2023-09-22-github-actions-transitioning-from-node-16-to-node-20/. Show more buildhttps://github.com/epfaffinger/AzureNamingTool/actions/runs/8298362409/job/22711571597 Node.js 16 actions are deprecated. Please update the following actions to use Node.js 20: @., @., @., @. For more information see: https://github.blog/changelog/2023-09-22-github-actions-transitioning-from-node-16-to-node-20/. Show more build: src/Helpers/ConfigurationHelper.cs#L988https://github.com/epfaffinger/AzureNamingTool/commit/9350bec2fabc48a3a1d92abe72fed937272e5ecb#annotation_19331958215 Converting null literal or possible null value to non-nullable type. build: tests/AzureNamingTool.UiTests/HostAddressDetails.cs#L5https://github.com/epfaffinger/AzureNamingTool/commit/9350bec2fabc48a3a1d92abe72fed937272e5ecb#annotation_19331958226 Non-nullable property 'Address' must contain a non-null value when exiting constructor. Consider declaring the property as nullable. build: tests/AzureNamingTool.UiTests/Contexts/ContextBase.cs#L33https://github.com/epfaffinger/AzureNamingTool/commit/9350bec2fabc48a3a1d92abe72fed937272e5ecb#annotation_19331958240 Dereference of a possibly null reference. build: tests/AzureNamingTool.UiTests/Contexts/ContextBase.cs#L38https://github.com/epfaffinger/AzureNamingTool/commit/9350bec2fabc48a3a1d92abe72fed937272e5ecb#annotation_19331958247 Dereference of a possibly null reference. build: tests/AzureNamingTool.UiTests/Contexts/ContextBase.cs#L43https://github.com/epfaffinger/AzureNamingTool/commit/9350bec2fabc48a3a1d92abe72fed937272e5ecb#annotation_19331958256 Dereference of a possibly null reference. build: src/Helpers/ConfigurationHelper.cs#L988https://github.com/epfaffinger/AzureNamingTool/commit/9350bec2fabc48a3a1d92abe72fed937272e5ecb#annotation_19331958266 Converting null literal or possible null value to non-nullable type. build: tests/AzureNamingTool.UiTests/HostAddressDetails.cs#L5https://github.com/epfaffinger/AzureNamingTool/commit/9350bec2fabc48a3a1d92abe72fed937272e5ecb#annotation_19331958281 Non-nullable property 'Address' must contain a non-null value when exiting constructor. Consider declaring the property as nullable. build: tests/AzureNamingTool.UiTests/Contexts/ContextBase.cs#L33https://github.com/epfaffinger/AzureNamingTool/commit/9350bec2fabc48a3a1d92abe72fed937272e5ecb#annotation_19331958298 Dereference of a possibly null reference. build: tests/AzureNamingTool.UiTests/Contexts/ContextBase.cs#L38https://github.com/epfaffinger/AzureNamingTool/commit/9350bec2fabc48a3a1d92abe72fed937272e5ecb#annotation_19331958312 Dereference of a possibly null reference. build: tests/AzureNamingTool.UiTests/Contexts/ContextBase.cs#L43https://github.com/epfaffinger/AzureNamingTool/commit/9350bec2fabc48a3a1d92abe72fed937272e5ecb#annotation_19331958327 Dereference of a possibly null reference. buildhttps://github.com/epfaffinger/AzureNamingTool/actions/runs/8298362409/job/22711571597#step:6:36 The "--output" option isn't supported when building a solution. Specifying a solution-level output path results in all projects copying outputs to the same directory, which can lead to inconsistent builds. deployhttps://github.com/epfaffinger/AzureNamingTool/actions/runs/8298362409/job/22711653333 Node.js 16 actions are deprecated. Please update the following actions to use Node.js 20: @., @.*** For more information see: https://github.blog/changelog/2023-09-22-github-actions-transitioning-from-node-16-to-node-20/. Show more deployhttps://github.com/epfaffinger/AzureNamingTool/actions/runs/8298362409/job/22711653333#step:4:2 Skip setting environment url as environment 'Development' may contain secret.

In the meantime, I will try to publish v4.0.1 via the zip file from Visual Studio Code.

Thanks, Eric

From: Bryan Soltis @.> Sent: Friday, March 15, 2024 11:33 AM To: mspnp/AzureNamingTool @.> Cc: Eric Pfaffinger @.>; Mention @.> Subject: Re: [mspnp/AzureNamingTool] Deployed 4.1.0 and just getting default Azure App Service page. (Issue #94)

CAUTION: This email originated from outside of Equitable Life. Do not click links or open attachments unless you recognize the sender and know the content is safe.

Hi @epfaffingerhttps://github.com/epfaffinger,

Thank you for your feedback, but sorry to hear you're having issues. We haven't recieved any reports of any trouble deploying, so I am curious as to why yours is not working.

For v4.1.0:

image.png (view on web)https://github.com/mspnp/AzureNamingTool/assets/13591910/f5b6ff04-e604-4ce0-81c7-a74cd4001af5

For v4.0.1:

https://learn.microsoft.com/en-us/visualstudio/deployment/deploying-applications-services-and-components-resources?view=vs-2022#azure

Hope this helps. Let me know if you find anything in your logs/findings and I'll if I can figure out why yours is failing.

— Reply to this email directly, view it on GitHubhttps://github.com/mspnp/AzureNamingTool/issues/94#issuecomment-1999918353, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AQNY6HXRP5QFYVZRNTOQNY3YYMIDXAVCNFSM6AAAAABEWX4P3WVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTSOJZHEYTQMZVGM. You are receiving this because you were mentioned.Message ID: @.**@.>>

IMPORTANT NOTICE: Internet may be vulnerable to interception. Equitable Life cannot ensure privacy or authenticity of information sent via internet, and is not responsible for any damages you incur by sending confidential or personal information to us or by sending such information to you at your request. This e-mail and any attachments are confidential, may be covered by privilege or exempt from disclosure under applicable law, and are intended for the addressee only. If you are not the intended recipient, you must not disclose, copy, distribute or retain any or part of this e-mail and any attachments without written permission of The Equitable Life Insurance Company of Canada.

AVIS IMPORTANT : L'Internet est susceptible Ă  l'interception. L'Assurance vie Équitable ne peut garantir le droit Ă  la vie privĂ©e et l'authenticitĂ© des renseignements envoyĂ©s par l'entremise de l'Internet, et elle n'est pas responsable de tout dommage que vous pourriez subir en nous envoyant vos renseignements personnels ou confidentiels ou si nous vous envoyons de tels renseignements Ă  la suite de votre demande. Ce courriel et ses piĂšces jointes sont confidentiels, et peuvent ĂȘtre protĂ©gĂ©s par une clause de non-divulgation selon la loi applicable, et s'adressent Ă  la destinataire ou au destinataire seulement. Si vous n'ĂȘtes pas le destinataire visĂ© de ce courriel et de ses piĂšces jointes, vous ne devez pas les divulguer, les copier, les distribuer ou les conserver en tout ou en partie sans la permission Ă©crite de L'Équitable, compagnie d'assurance vie du Canada.

epfaffinger commented 6 months ago

Hi @Bryan @.***>,

Not sure if this helps but I redeployed to an Azure App Service where the app service plan was set to Windows rather than Linux and the naming tool app loads and functions correctly. However, deploying to an app service with a Linux based app service plan does not?

From: Bryan Soltis @.> Sent: Friday, March 15, 2024 11:33 AM To: mspnp/AzureNamingTool @.> Cc: Eric Pfaffinger @.>; Mention @.> Subject: Re: [mspnp/AzureNamingTool] Deployed 4.1.0 and just getting default Azure App Service page. (Issue #94)

CAUTION: This email originated from outside of Equitable Life. Do not click links or open attachments unless you recognize the sender and know the content is safe.

Hi @epfaffingerhttps://github.com/epfaffinger,

Thank you for your feedback, but sorry to hear you're having issues. We haven't recieved any reports of any trouble deploying, so I am curious as to why yours is not working.

For v4.1.0:

image.png (view on web)https://github.com/mspnp/AzureNamingTool/assets/13591910/f5b6ff04-e604-4ce0-81c7-a74cd4001af5

For v4.0.1:

https://learn.microsoft.com/en-us/visualstudio/deployment/deploying-applications-services-and-components-resources?view=vs-2022#azure

Hope this helps. Let me know if you find anything in your logs/findings and I'll if I can figure out why yours is failing.

- Reply to this email directly, view it on GitHubhttps://github.com/mspnp/AzureNamingTool/issues/94#issuecomment-1999918353, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AQNY6HXRP5QFYVZRNTOQNY3YYMIDXAVCNFSM6AAAAABEWX4P3WVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTSOJZHEYTQMZVGM. You are receiving this because you were mentioned.Message ID: @.**@.>>

IMPORTANT NOTICE: Internet may be vulnerable to interception. Equitable Life cannot ensure privacy or authenticity of information sent via internet, and is not responsible for any damages you incur by sending confidential or personal information to us or by sending such information to you at your request. This e-mail and any attachments are confidential, may be covered by privilege or exempt from disclosure under applicable law, and are intended for the addressee only. If you are not the intended recipient, you must not disclose, copy, distribute or retain any or part of this e-mail and any attachments without written permission of The Equitable Life Insurance Company of Canada.

AVIS IMPORTANT : L'Internet est susceptible ? l'interception. L'Assurance vie ?quitable ne peut garantir le droit ? la vie priv?e et l'authenticit? des renseignements envoy?s par l'entremise de l'Internet, et elle n'est pas responsable de tout dommage que vous pourriez subir en nous envoyant vos renseignements personnels ou confidentiels ou si nous vous envoyons de tels renseignements ? la suite de votre demande. Ce courriel et ses pi?ces jointes sont confidentiels, et peuvent ?tre prot?g?s par une clause de non-divulgation selon la loi applicable, et s'adressent ? la destinataire ou au destinataire seulement. Si vous n'?tes pas le destinataire vis? de ce courriel et de ses pi?ces jointes, vous ne devez pas les divulguer, les copier, les distribuer ou les conserver en tout ou en partie sans la permission ?crite de L'?quitable, compagnie d'assurance vie du Canada.

epfaffinger commented 6 months ago

Sorry I meant to say that the deploy works on a Windows based App Service but not Linux in my case.

From: Eric Pfaffinger @.> Sent: Friday, March 15, 2024 3:58 PM To: mspnp/AzureNamingTool @.>; mspnp/AzureNamingTool @.>; Bryan Soltis @.> Cc: Mention @.***> Subject: RE: [mspnp/AzureNamingTool] Deployed 4.1.0 and just getting default Azure App Service page. (Issue #94)

Hi @Bryan @.***>,

Not sure if this helps but I redeployed to an Azure App Service where the app service plan was set to Windows rather than Linux and the naming tool app loads and functions correctly. However, deploying to an app service with a Linux based app service plan does not?

From: Bryan Soltis @.**@.>> Sent: Friday, March 15, 2024 11:33 AM To: mspnp/AzureNamingTool @.**@.>> Cc: Eric Pfaffinger @.**@.>>; Mention @.**@.>> Subject: Re: [mspnp/AzureNamingTool] Deployed 4.1.0 and just getting default Azure App Service page. (Issue #94)

CAUTION: This email originated from outside of Equitable Life. Do not click links or open attachments unless you recognize the sender and know the content is safe.

Hi @epfaffingerhttps://github.com/epfaffinger,

Thank you for your feedback, but sorry to hear you're having issues. We haven't recieved any reports of any trouble deploying, so I am curious as to why yours is not working.

For v4.1.0:

image.png (view on web)https://github.com/mspnp/AzureNamingTool/assets/13591910/f5b6ff04-e604-4ce0-81c7-a74cd4001af5

For v4.0.1:

https://learn.microsoft.com/en-us/visualstudio/deployment/deploying-applications-services-and-components-resources?view=vs-2022#azure

Hope this helps. Let me know if you find anything in your logs/findings and I'll if I can figure out why yours is failing.

- Reply to this email directly, view it on GitHubhttps://github.com/mspnp/AzureNamingTool/issues/94#issuecomment-1999918353, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AQNY6HXRP5QFYVZRNTOQNY3YYMIDXAVCNFSM6AAAAABEWX4P3WVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTSOJZHEYTQMZVGM. You are receiving this because you were mentioned.Message ID: @.**@.>>

IMPORTANT NOTICE: Internet may be vulnerable to interception. Equitable Life cannot ensure privacy or authenticity of information sent via internet, and is not responsible for any damages you incur by sending confidential or personal information to us or by sending such information to you at your request. This e-mail and any attachments are confidential, may be covered by privilege or exempt from disclosure under applicable law, and are intended for the addressee only. If you are not the intended recipient, you must not disclose, copy, distribute or retain any or part of this e-mail and any attachments without written permission of The Equitable Life Insurance Company of Canada.

AVIS IMPORTANT : L'Internet est susceptible ? l'interception. L'Assurance vie ?quitable ne peut garantir le droit ? la vie priv?e et l'authenticit? des renseignements envoy?s par l'entremise de l'Internet, et elle n'est pas responsable de tout dommage que vous pourriez subir en nous envoyant vos renseignements personnels ou confidentiels ou si nous vous envoyons de tels renseignements ? la suite de votre demande. Ce courriel et ses pi?ces jointes sont confidentiels, et peuvent ?tre prot?g?s par une clause de non-divulgation selon la loi applicable, et s'adressent ? la destinataire ou au destinataire seulement. Si vous n'?tes pas le destinataire vis? de ce courriel et de ses pi?ces jointes, vous ne devez pas les divulguer, les copier, les distribuer ou les conserver en tout ou en partie sans la permission ?crite de L'?quitable, compagnie d'assurance vie du Canada.

epfaffinger commented 6 months ago

I think I found the issue, this may be in your documentation somewhere but I didn't see it if it was but for a Linux based deploy after upgrading you need to go to the app service config general settings and specifiy the startup command as shown below:

[A screenshot of a computer Description automatically generated]

From: Eric Pfaffinger Sent: Friday, March 15, 2024 4:09 PM To: mspnp/AzureNamingTool @.>; mspnp/AzureNamingTool @.>; Bryan Soltis @.> Cc: Mention @.> Subject: RE: [mspnp/AzureNamingTool] Deployed 4.1.0 and just getting default Azure App Service page. (Issue #94)

Sorry I meant to say that the deploy works on a Windows based App Service but not Linux in my case.

From: Eric Pfaffinger @.**@.>> Sent: Friday, March 15, 2024 3:58 PM To: mspnp/AzureNamingTool @.**@.>>; mspnp/AzureNamingTool @.**@.>>; Bryan Soltis @.**@.>> Cc: Mention @.**@.>> Subject: RE: [mspnp/AzureNamingTool] Deployed 4.1.0 and just getting default Azure App Service page. (Issue #94)

Hi @Bryan @.***>,

Not sure if this helps but I redeployed to an Azure App Service where the app service plan was set to Windows rather than Linux and the naming tool app loads and functions correctly. However, deploying to an app service with a Linux based app service plan does not?

From: Bryan Soltis @.**@.>> Sent: Friday, March 15, 2024 11:33 AM To: mspnp/AzureNamingTool @.**@.>> Cc: Eric Pfaffinger @.**@.>>; Mention @.**@.>> Subject: Re: [mspnp/AzureNamingTool] Deployed 4.1.0 and just getting default Azure App Service page. (Issue #94)

CAUTION: This email originated from outside of Equitable Life. Do not click links or open attachments unless you recognize the sender and know the content is safe.

Hi @epfaffingerhttps://github.com/epfaffinger,

Thank you for your feedback, but sorry to hear you're having issues. We haven't recieved any reports of any trouble deploying, so I am curious as to why yours is not working.

For v4.1.0:

image.png (view on web)https://github.com/mspnp/AzureNamingTool/assets/13591910/f5b6ff04-e604-4ce0-81c7-a74cd4001af5

For v4.0.1:

https://learn.microsoft.com/en-us/visualstudio/deployment/deploying-applications-services-and-components-resources?view=vs-2022#azure

Hope this helps. Let me know if you find anything in your logs/findings and I'll if I can figure out why yours is failing.

- Reply to this email directly, view it on GitHubhttps://github.com/mspnp/AzureNamingTool/issues/94#issuecomment-1999918353, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AQNY6HXRP5QFYVZRNTOQNY3YYMIDXAVCNFSM6AAAAABEWX4P3WVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTSOJZHEYTQMZVGM. You are receiving this because you were mentioned.Message ID: @.**@.>>

IMPORTANT NOTICE: Internet may be vulnerable to interception. Equitable Life cannot ensure privacy or authenticity of information sent via internet, and is not responsible for any damages you incur by sending confidential or personal information to us or by sending such information to you at your request. This e-mail and any attachments are confidential, may be covered by privilege or exempt from disclosure under applicable law, and are intended for the addressee only. If you are not the intended recipient, you must not disclose, copy, distribute or retain any or part of this e-mail and any attachments without written permission of The Equitable Life Insurance Company of Canada.

AVIS IMPORTANT : L'Internet est susceptible ? l'interception. L'Assurance vie ?quitable ne peut garantir le droit ? la vie priv?e et l'authenticit? des renseignements envoy?s par l'entremise de l'Internet, et elle n'est pas responsable de tout dommage que vous pourriez subir en nous envoyant vos renseignements personnels ou confidentiels ou si nous vous envoyons de tels renseignements ? la suite de votre demande. Ce courriel et ses pi?ces jointes sont confidentiels, et peuvent ?tre prot?g?s par une clause de non-divulgation selon la loi applicable, et s'adressent ? la destinataire ou au destinataire seulement. Si vous n'?tes pas le destinataire vis? de ce courriel et de ses pi?ces jointes, vous ne devez pas les divulguer, les copier, les distribuer ou les conserver en tout ou en partie sans la permission ?crite de L'?quitable, compagnie d'assurance vie du Canada.

epfaffinger commented 6 months ago

This is resolved, for Linux you need to put the following in the startup command box in the general config of the app service:

dotnet AzureNamingTool.dll

BryanSoltis commented 6 months ago

Hi Eric,

A couple of things. First, THANK YOU for all of your feedback and experience with the tool. Hearing from our users is the only way we can improve and ensure the tool is meeting your needs. Second, that's great that you were able to figure out the issue! We did not have that startup command in our documentation, so your feedback helped improve the installation experience. I have added a note to the App Service/GitHub instructions, along with a screenshot.

Thank you again for the great information and please let us know if you encounter any more issues!

epfaffinger commented 6 months ago

Hi Bryan,

Thank you for helping develop such a useful tool! It's definitely improved the Azure naming process for us!

Cheers, Eric

From: Bryan Soltis @.> Sent: Monday, March 18, 2024 10:20 AM To: mspnp/AzureNamingTool @.> Cc: Eric Pfaffinger @.>; State change @.> Subject: Re: [mspnp/AzureNamingTool] Deployed 4.1.0 and just getting default Azure App Service page. (Issue #94)

CAUTION: This email originated from outside of Equitable Life. Do not click links or open attachments unless you recognize the sender and know the content is safe.

Hi Eric,

A couple of things. First, THANK YOU for all of your feedback and experience with the tool. Hearing from our users is the only way we can improve and ensure the tool is meeting your needs. Second, that's great that you were able to figure out the issue! We did not have that startup command in our documentation, so your feedback helped improve the installation experience. I have added a note to the App Service/GitHub instructions, along with a screenshot.

Thank you again for the great information and please let us know if you encounter any more issues!

- Reply to this email directly, view it on GitHubhttps://github.com/mspnp/AzureNamingTool/issues/94#issuecomment-2004048480, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AQNY6HSLA5CQ4LAFRFEE5ELYY3ZZ5AVCNFSM6AAAAABEWX4P3WVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDAMBUGA2DQNBYGA. You are receiving this because you modified the open/close state.Message ID: @.**@.>>

IMPORTANT NOTICE: Internet may be vulnerable to interception. Equitable Life cannot ensure privacy or authenticity of information sent via internet, and is not responsible for any damages you incur by sending confidential or personal information to us or by sending such information to you at your request. This e-mail and any attachments are confidential, may be covered by privilege or exempt from disclosure under applicable law, and are intended for the addressee only. If you are not the intended recipient, you must not disclose, copy, distribute or retain any or part of this e-mail and any attachments without written permission of The Equitable Life Insurance Company of Canada.

AVIS IMPORTANT : L'Internet est susceptible ? l'interception. L'Assurance vie ?quitable ne peut garantir le droit ? la vie priv?e et l'authenticit? des renseignements envoy?s par l'entremise de l'Internet, et elle n'est pas responsable de tout dommage que vous pourriez subir en nous envoyant vos renseignements personnels ou confidentiels ou si nous vous envoyons de tels renseignements ? la suite de votre demande. Ce courriel et ses pi?ces jointes sont confidentiels, et peuvent ?tre prot?g?s par une clause de non-divulgation selon la loi applicable, et s'adressent ? la destinataire ou au destinataire seulement. Si vous n'?tes pas le destinataire vis? de ce courriel et de ses pi?ces jointes, vous ne devez pas les divulguer, les copier, les distribuer ou les conserver en tout ou en partie sans la permission ?crite de L'?quitable, compagnie d'assurance vie du Canada.