Skip to content

Conversation

@colerogers
Copy link
Contributor

@colerogers colerogers commented Jul 28, 2021

Description

Creating a way for customers to explicitly set the access control on HTTP triggered functions. The access control is set at the function level, so different functions can have different access policies. The customer can choose to set access control to public, private, or a custom service account. Access control is set in the runWith() function by setting the property invoker. To handle multiple service accounts, invoker can accept an array of strings.

The corresponding firebase-tools PR is here

Code sample

export const myHttpFunc = runWith({invoker: "private"}).onRequest((req, res) => { res.send({hello: "private"}); });

@google-cla google-cla bot added the cla: yes label Jul 28, 2021
@colerogers colerogers requested a review from joehan July 28, 2021 17:47
@colerogers colerogers changed the title Set Access Control for HTTP Functions Set Access Control for HTTP Functions (v1) Jul 29, 2021
@colerogers colerogers requested a review from inlined July 29, 2021 20:13
@colerogers colerogers self-assigned this Jul 29, 2021
Copy link
Contributor

@joehan joehan left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Some minor feedback, but this mostly LGTM

@colerogers colerogers merged commit 63a0cc4 into master Aug 2, 2021
@inlined inlined deleted the colerogers.http-access-control branch August 10, 2021 16:55
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants