Node PR Environments fail if you use Environment Variables.

[sig9]

If you have a node app that has serverless functions, your first deployment from a PR will not see the configuration variables that are visible in the portal. Your options are to re-deploy or use the portal to modify and save a configuration variable for the PR environment.

At a minimum, this should be stated as a limitation if nobody is going to acknowledge or work on issue/914.

https://github.com/Azure/static-web-apps/issues/914 See also support ticket 2209180010000070

---

Document Details

⚠ Do not edit this section. It is required for learn.microsoft.com ➟ GitHub issue linking.

• ID: c1fbc397-f3ea-dc49-ec99-a77e824752e0
• Version Independent ID: 7524eee9-a9a6-07f6-acb5-b008a02d6078
• Content: Review pull requests in pre-production environments
• Content Source: articles/static-web-apps/review-publish-pull-requests.md
• Service: static-web-apps
• GitHub Login: @sinedied
• Microsoft Alias: yolasors

[RamanathanChinnappan-MSFT]

@sig9

Thanks for your feedback! We will investigate and update as appropriate.

[binkiesjoris]

Aye, if this is an intended change (as it used to work fine) it would be nice to have the documentation reflect this change.

[Venkateshdodda-MSFT]

@sig9 Thanks for your patience on this, I have checked with static webapps engineering team on this, and they have confirmed that the fix has been deployed and this doesn't require any document change. In the other referenced GitHub issue #914 it is confirmed that customers are not facing this issue. We will close this out, but if you feel you need more information, please just let us know.