You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Not really familiar with Azure static web apps :)
I am trying to understand what exactly the benefits are in comparison to static hosting and an azure function which can be already handled by nx-deploy-it
So currently I can already create a nx workspace with an angular app and nestjs as backend.
Both are deployable with Nx DeployIt
frontend with cdn
backend as serverless function
The only thing which is currently missing is the automated dependency (infrastructure urls) to each other. Means you need to deploy first the backend and use the created endpoint with the frontend.
How can a Azure static app help here? What makes it different?
Ok just read a bit more about it now and see some key features.
Thinking about how this could be integrated...
Nx DeployIt is asking at the beginning (scan schematic) which application you want to integrate with infrastructure as code.
Option A:
If you select minimum a frontend app with azure option we could ask him how to deploy it
static hosting
static web app
Option B:
If you select a frontend and a backend app with azure option we could ask him to combine both as Static web app -> This way we have the full potential of the static web app with frontend and backend together
The next thing is that Nx DeployIt is working with Pulumi under the hood.
Currently there is no Static Web App resource.
Here again 2 options:
Option A:
Waiting for the support in terraform / pulumi
Option B:
Writing our own Component / Custom Resources which is provisioning the Static Web App based on azure cli commands (if azure self already supports this -> i guess it's this one)
Activity
MitkoTschimev commentedon May 26, 2020
Not really familiar with Azure static web apps :)
I am trying to understand what exactly the benefits are in comparison to static hosting and an azure function which can be already handled by nx-deploy-it
So currently I can already create a nx workspace with an angular app and nestjs as backend.
Both are deployable with Nx DeployIt
The only thing which is currently missing is the automated dependency (infrastructure urls) to each other. Means you need to deploy first the backend and use the created endpoint with the frontend.
How can a Azure static app help here? What makes it different?
MitkoTschimev commentedon May 26, 2020
Ok just read a bit more about it now and see some key features.
Thinking about how this could be integrated...
Nx DeployIt is asking at the beginning (scan schematic) which application you want to integrate with infrastructure as code.
Option A:
If you select minimum a frontend app with azure option we could ask him how to deploy it
Option B:
If you select a frontend and a backend app with azure option we could ask him to combine both as Static web app -> This way we have the full potential of the static web app with frontend and backend together
The next thing is that Nx DeployIt is working with Pulumi under the hood.
Currently there is no Static Web App resource.
Here again 2 options:
Option A:
Waiting for the support in terraform / pulumi
Option B:
Writing our own Component / Custom Resources which is provisioning the Static Web App based on azure cli commands (if azure self already supports this -> i guess it's this one)
manekinekko commentedon May 26, 2020
Azure Static Web Apps is still in preview. CLI support is not available yet (
az webappis another service).Here are all the benefits of switching to SWA comparing to blob storage:
So, if you are using Plumi for Azure management, then you probably need to wait for them to add SWA support.
Cheers.
MitkoTschimev commentedon May 27, 2020
Than we have to wait a bit till Microsoft provides all the APIs to create this recourses.
After that terraform / pulumi is really quick to adapt and we can for sure integrate it in a beautiful way
manekinekko commentedon May 27, 2020
We already provide the ARM template to create and manage your SWA instances. However, they are still in PREVIEW ;)
MitkoTschimev commentedon May 27, 2020
Preview is ok ;) but if you already provide an ARM template its perfect!!
We can use this resource from pulumi!
https://github.com/pulumi/examples/blob/master/azure-ts-arm-template/index.ts
MitkoTschimev commentedon Dec 25, 2020
I think there is finally a solution in pulumi available
@manekinekko Can you verify if this is the resource for a static web app?
manekinekko commentedon Jan 22, 2021
@MitkoTschimev I don't so because we haven't published official ARM template for SWA yet. So this plugin might be creating a App Service.