Pre-Production environments: Allow for more than 10 pre-production environments

[Strepto]

Is your feature request related to a problem? Please describe.

We are a team with a few developers, trying to do our development work with a bunch of pull requests, and pull-request environments. Currently we have a few spikes that are waiting for feedback, and a number of ongoing work in other draft and open pull requests.

Today this meant that we had 10 open pull requests, and when a 11th was opened it could not be deployed as we only have 10 Pre-Production environments in the Azure SWA.

Describe the solution you'd like

I would like to be able to have more than 10 pre-production environments for a Azure Static Web App. I could pay more for this.

Describe alternatives you've considered

Changing to other similar hosting solutions, or rewriting our pull request environments to be folder based in instead of domain based.

[Strepto]

Any chance of this? We are frequently hitting the 10 PR environment limit.

[superhp]

+1 There should be an option to at least buy additional PR environments. There is also a limitation of max app size which might suddenly become an issue as well. Maybe there could be a more professional plan option to buy which don't have such hard limits.

[Strepto]

Any updates on this? See also: #941 for a similar request.

[thomasgauvin]

This is good feedback, thank you @Strepto and @superhp. We'll look into providing more preview environments. What would be a rough number that would be sufficient for your use cases, if you were to give an estimate? This could help us planning this improvement

[Strepto]

We are not using any of the "function" features in our app, so for us SWA is just serving static files and providing Urls. Today (2022-10-25) we have to juggle the 10 environments between ~12 more or less active PRs. So for today about 20 environments would give us a buffer. This number slowly increases due to spikes, working branches, demos etc. Maybe 25 or 50 would be good numbers to provide as options.

[mattdot]

Also using Preview Sites in the same way as Strepto is for static content only following this guidance https://learn.microsoft.com/en-us/azure/static-web-apps/review-publish-pull-requests. Our use case is a docs repo with a large number of contributors (100 active), so it's really hard to predict the number of open PRs at any one time. We don't want to tell people not to open PRs, and it's hard to explain why sometimes preview sites work and sometimes they don't.

10 is way too low. Ideally it wouldn't be an arbitrary number and would just bill us for as many additional sites as we are using. But if you do pick an arbitrary number like 50, please make it able to be overridden by a support request for special cases.

[thomasgauvin]

Thanks @Strepto and @mattdot, this is good feedback and I'm taking note of it. We're currently working on improving our content distribution and that engineering work would enable us to consider these increases, I will keep this thread updated as we progress

[tobiasdiez]

@thomasgauvin any update here? The limit of 10 environments is also pretty annoying for smaller teams, since dependabot easily opens more PRs.

[jmburns]

Also very interested in knowing the status of this. Our team is also only hosting the static files for a react app with no back-end code. If a way to increase the limit is not coming we will likely switch away from Static Web Apps.

[MTCMarkFranco]

update to this?

[thomasgauvin]

We've heard the feedback and have been putting in the infrastructural improvements to have increased limits across the board for Static Web Apps, whether that be number of staging envs, file counts, app sizes, etc. We're still some months away from this at this time, I will continue to provide status updates in this thread.

[gterminator]

Any update here? We have 2024...

[Squixx]

Also waiting for this, any updates?

[tnmygrwl]

Waiting for an update too! Additionally, is there a way to just remove the manually deleting component from this process, could we not auto-delete envs based on some policy e.g. earliest PR envs get deleted for new ones.

[nitelite]

I would love to be able to pay for more staging environments, just give me a slider and charge my bill.

[gterminator]

Maybe I start my own "static web pages"-service. I see there are enough people paying for that.

[Squixx]

I would love to be able to pay for more staging environments, just give me a slider and charge my bill.

Same here. I could add a couple of more SWA instances to work around it, but just being able to pay more would be preferable

[remcohuijser]

We are using the staging environments as previews during development and now that the team is growing, we could really use more than 10 slots for this. Please consider increasing this limit.

[nitelite]

We've heard the feedback and have been putting in the infrastructural improvements to have increased limits across the board for Static Web Apps, whether that be number of staging envs, file counts, app sizes, etc. We're still some months away from this at this time, I will continue to provide status updates in this thread.

Please let me pay you more money. You can charge me the same as an entire SWA resource for each preview environment over the 10th, if you just give me a slider to pull on to increase the max number.