We use Nerdio with private endpoints and when we Upgrade we have to deploy using the zip push method. We would really like to be able to use the deploy button to upgrade nerdio. Making the ease of upgrade better, consistent and less risk of user failure.
Nerdio Upgrade with private endpoints, please allow the deploy button to work and not have to do the zip push
5
We appreciate your feature request—community input is essential to our ongoing development.
Next steps:
• We will review your suggestion and update its status during the evaluation process.
• If further clarification is needed, we'll contact you via comments.
We also encourage others to contribute through feedback and voting.
Next steps:
• We will review your suggestion and update its status during the evaluation process.
• If further clarification is needed, we'll contact you via comments.
We also encourage others to contribute through feedback and voting.
If you build a Hybrid worker group in the automation account (default: nmw-app-automation-uniqueidentifier) and add a worker VM to the private vnet (or peered vnet) NME will ask if you want to use it when clicking the update/Deploy button. This will allow the update to run in the automation account and not require you to do the manual zip deploy.

I will still take an action to get this feature better documented in our KBs
thanks! Let me know if that helps.
Please sign in to leave a comment.
Comments (2 comments)