Quickstart template repo no longer exists about azure-health-data-services-toolkit HOT 8 CLOSED

Hi @pjirsa , we are in the middle of fixing up our quickstart template, I'll let you know when it's fixed and ready to go!

from azure-health-data-services-toolkit.

@kyle-mwnz Thanks for your patience! We just merged a PR that should fix this, please make sure you have the most recent version of the main branch and deploy the quickstart with the new instructions: https://github.com/microsoft/azure-health-data-services-toolkit/tree/main/samples/Quickstart . Please let us know if you still run into issues!

from azure-health-data-services-toolkit.

@evachen96 LMK how I can help!

from azure-health-data-services-toolkit.

@evachen96 Are there any other options available to get started?

I have tried the Quickstart in this repo as opposed to the one which seems to have been removed, but I'm having to work through a large number of issues. The most recent one is Failed to start a new language worker for runtime: dotnet-isolated. when attempting to call the Function app

azd provision fails with

ERROR: deployment failed: failing invoking action 'provision', error deploying infrastructure: deploying to subscription:

Deployment Error Details:
BadRequest: Encountered an error (ServiceUnavailable) from host runtime.
- Encountered an error (ServiceUnavailable) from host runtime.

from azure-health-data-services-toolkit.

@kyle-mwnz We are still working on getting the quickstart fixed, but one workaround that we've found is that if you re-run the quickstart (azd provision again) then it should work on the second try. @erikhoward can help if you have more questions. I'll update when we have a permanent fix. Thanks for your patience!

from azure-health-data-services-toolkit.

Running a subsequent azd provision removes the error returned from the CLI, but the resource still seems to be in an unusable state after running azd deploy. There are errors relating to the .net version when publishing - the readme and iac seems to target .net6, but there is a globals.json file targeting v7? I have tried deploying with all the Iac etc updated to use v7 but the same error below occurs

When it is in this state requests to the function return a 502 html page which appears to be from nginx, and a log Failed to start a new language worker for runtime: dotnet-isolated. in app insights

I'll probably need to pause this and wait for a quickstart template to be available - I only have a couple of days to evaluate if this will work for use at a client

from azure-health-data-services-toolkit.

@kyle-mwnz You should be able to modify the global .json file and change it to the .NET version that you're using, let me know if that works!

from azure-health-data-services-toolkit.

As mentioned - I've tried many combinations of .NET versions, the Function app is still in the above error state

from azure-health-data-services-toolkit.