-
Notifications
You must be signed in to change notification settings - Fork 74
Update sources event CE types, sources, subjects #1340
Conversation
Skipping CI for Draft Pull Request. |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: yolocs The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
/test all |
CloudAuditLogsSourceLogWrittenEventType = "google.cloud.audit.log.v1.written" | ||
CloudAuditLogsSourceEventDataSchema = "https://github.com/googleapis/google-cloudevents/blob/master/proto/google/events/cloud/audit/v1/events.proto" |
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.
can we put all of these constants in register.go
maybe? outside v1beta1... When we do v1, we will be copy/pasting them otherwise. Similar thing happened with the current values... They are both in v1alpha1 and v1beta1
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.
That's a good point!
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 actually moved this out of the apis
folder. I feel it makes more sense as they eventually should be replaced by the code generated from the protos.
Still trying to make sure the e2e tests are not broken |
/test all |
/retest |
/test all |
/test all |
/test all |
/test pull-google-knative-gcp-integration-tests |
/test all |
Is this still in draft? Can we get this in and maybe do follow ups if needed? @zargarpur would benefit from some of this constants in a change he is doing for metrics... |
/lgtm I reviewed yesterday. Just looked at the updates, looks great! Thanks a lot @yolocs for doing this. Can we create a new issue to update the examples in this repo? and we can probably ask some new member to help with that? Similarly, I think we need to discuss what are we going to do with current OSS users... Whether we are planning on updating their Triggers (if any is filtering based on old info), or we just have a huge Action Required in the notes... |
#1355 for doc updates. |
Thanks @yolocs!The summary of the string changes in the release notes is great. I wrote this summary of the
|
/retest |
2 similar comments
/retest |
/retest |
The following jobs failed:
Job pull-google-knative-gcp-wi-tests expended all 3 retries without success. |
Fixes #1209
Proposed Changes
Release Note
Docs