-
Notifications
You must be signed in to change notification settings - Fork 202
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
Added eventarc onCustomEventPublished API #1061
Conversation
f4c98df
to
ab337eb
Compare
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.
Picked out a few style nits in the comments that get parsed for docgen. Thanks!
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.
Sorry, I meant to just comment, not approve (yet). Does this fix that? :)
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.
You'd also want to update package.json, e.g.
LGTM - deferring approval to @colerogers
edf2f82
to
12cbeef
Compare
{ | ||
...FULL_OPTIONS, | ||
eventType: 'event-type', | ||
channel: 'locations/us-west1/channels/my-channel', |
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.
Per the partial resource name resolution, I think we should also have a test that verifies "my-channel" gets turned into locations/us-central1/channels/my-channel
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.
On the functions SDK side I'm only doing the: if channel is not specified, default it to 'locations/us-central1/channels/firebase'. The rest of the partial channel resource name resolution (and validation) is done on the CLI side.
The reason it's done this way is because if channel is not specified, in the container contract I can't distinguish between: it's not specified and expected to be resolved to default
vs not specified and should remain undefined
.
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.
Sounds good. And the more code we put in the "agent" (e.g. CLI, control plane) the less we have to redefine in the SDKs.
Co-authored-by: Daniel Lee <taeold@gmail.com>
Co-authored-by: Daniel Lee <taeold@gmail.com>
f6c38c2
to
e9784de
Compare
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.
Still LGTM. @taeold can you take a pass if necessary and stamp this?
go/rvtfmkswhlks