Matthew Fisher
Matthew Fisher
Related for workload profiles: https://github.com/microsoft/vscode-azurecontainerapps/issues/580 Related for CPU and Memory configs: https://github.com/microsoft/vscode-azurecontainerapps/issues/743
This should eventually be fixed by: https://github.com/microsoft/vscode-azurefunctions/pull/4538
Just curious, what's the reason you're having to use an older version of the Resource Group's extension? We're hoping you can just switch to using the latest if it doesn't...
Edit: Investigating some more and after restarting VS Code this no longer reproduces. Really strange why this was happening the first time. Of note - when I ran into this...
The zip on the extension does not rely on those, but on the `yazl` npm package. We do have a release coming out soon that should allow you to deploy...
It is also reproducing on the current release for me.
Glad you were able to find a workaround!
Which method did you use to deploy to your static web app? Did you deploy with GitHub actions or use the static web apps cli, etc?
We have made a release recently that may have fixed the issue or at least improved the error messaging. Could you please let us know if you're still encountering the...
This may be an issue for Azure Resource Groups, but we'll need to investigate further before moving it over.