-
Notifications
You must be signed in to change notification settings - Fork 523
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
fix(cloud-function): disallow unauthenticated access #12710
base: main
Are you sure you want to change the base?
Conversation
We only need internal + load balancing ingress.
Bundle StatsHey there, this message comes from a github action that helps you and reviewers to understand how these changes affect the size of this project's bundle. As this PR is updated, I'll keep you updated on how the bundle size is impacted. Total
View detailed bundle breakdownAdded No assets were added Removed No assets were removed Bigger No assets were bigger Smaller No assets were smaller Unchanged
|
@@ -385,7 +385,6 @@ jobs: | |||
--region=$region \ | |||
--source=cloud-function \ | |||
--trigger-http \ | |||
--allow-unauthenticated \ |
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.
I suggest deploying this change to test/staging first to be sure nothing bad will happen?
Also: This looks strange:
Subsequent deployments of the same function don't change its status, even if you don't use this flag.
Summary
Problem
We set
--allow-unauthenticated
when deploying our Cloud Function, but this does not seem to be necessary, as we're routing internally from our GCP load balancer, as confirmed by the new Review function.Solution
Remove the
--allow-unauthenticated
flag.How did you test this change?
Applied the same change on the Review function, which is deployed, and can still be accessed through the load balancer (e.g. https://main.review.mdn.allizom.net/).