Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
fix : WAF deployment: private backend ingress and frontend proxy rou… #561
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: dev
Are you sure you want to change the base?
Uh oh!
There was an error while loading. Please reload this page.
fix : WAF deployment: private backend ingress and frontend proxy rou… #561
Changes from all commits
6bb94a01fd18c78c0985c7a4ed0dFile filter
Filter by extension
Conversations
Uh oh!
There was an error while loading. Please reload this page.
Jump to
Uh oh!
There was an error while loading. Please reload this page.
There are no files selected for viewing
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
With
ingressExternalset to false in private networking mode, the API Container App FQDN will no longer be reachable from outside the VNet. The repo's post-deployment scripts currently useCONTAINER_API_APP_FQDNto wait for readiness and register schemas from the deployer's machine; that flow will fail forenablePrivateNetworking=true. Consider updating the post-deployment workflow to call the API through the web app's new/apiproxy (usingCONTAINER_WEB_APP_FQDN) or to execute the registration from within the VNet (e.g., via the jumpbox).There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
With
ingressExternalset to false in private networking mode, the API Container App FQDN will no longer be reachable from outside the VNet. The repo's post-deployment scripts currently useCONTAINER_API_APP_FQDNto wait for readiness and register schemas from the deployer's machine; that flow will fail forenablePrivateNetworking=true. Consider updating the post-deployment workflow to call the API through the web app's new/apiproxy (usingCONTAINER_WEB_APP_FQDN) or to execute the registration from within the VNet (e.g., via the jumpbox).There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
location /api/relies onproxy_pass APP_BACKEND_API_URL/;being substituted at runtime. IfAPP_BACKEND_API_URLis not set in the container environment,env.shwill not replace the placeholder and nginx will fail to start due to an invalidproxy_passURL. Ensure all deployment paths that run this image always setAPP_BACKEND_API_URL(even when the app is not using the/apiproxy), or adjust the nginx config/entrypoint to provide a safe default when the variable is missing.Uh oh!
There was an error while loading. Please reload this page.