fix(security): Restore ADD_PROXY_ROUTE functionality for docker NGINX #4412
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.
This functionality was dropped in the Kong to NGINX change, and is being restored in order to make it easy to permanently add a custom route that survives "make clean" operations in Docker.
PR Checklist
Please check if your PR fulfills the following requirements:
BREAKING CHANGE:
describing the break)Testing Instructions
As per existing documentation, use ADD_PROXY_ROUTE on proxy-setup to add custom routes.
Verify changes to /etc/nginx/conf.d/custom-routes.inc and /etc/nginx/templates/custom-routes.inc.template
New Dependency Instructions (If applicable)