Yohan Lasorsa

The infra/backend already fully implement managed identity and do not make use of any API keys, is there any other requirements to implement?

Seems like the `postup` script did not run successfully. Could you try running `azd hooks run postup` to see you have additional debug messages/errors we could use? EDIT: Additionally, do...

Thanks for the details. I deployed a fresh environment from Codespaces and cannot reproduce the issue, I think it might be related to the environment. Could you share more information...

@manekinekko I've rebased the branch from develop, should be good now

Following our discussion, should we change the priority of this to P1 or P2 (in the case that we rework part of the infra, including APIM?)

> Hi @sinedied , is there any alternative that we can use instead of "wait-on" package? None that I know of. This is problematic in the whole Node.js ecosystem as...

> This is so painful from user perspective, may be we should try giving these params internally while starting the swa if the node version is 18. We can't do...

StaticSiteClient is not the only binary used the SWA CLI, there's also the Functions Core Tools. The problem is that there are many possible environments (win32, win64, macOS x64, macOS...

> Presently there is a devcontainer for SWA CLI, but it might be better to ship as a feature. Just to add a precision here, there are currently two container...

I'm not sure I understand what your issue is, do you have an example repo? The style for each component is scoped by default, you need to use something like...