Proto commits in googleapis/google-cloudevents

These 98 commits are when the Protocol Buffers files have changed:

2025-05-02

Add API Hub protos to google-cloudevents repo. PiperOrigin-RevId: 753866250

The documentation is generated from this commit.

2025-04-30

Add API Hub protos to google-cloudevents repo. PiperOrigin-RevId: 753085819

The documentation is generated from this commit.

2024-12-04

Add 'delivery_attempt' field in the Cloud Pub/Sub data schema. PiperOrigin-RevId: 702756217

2024-08-09

No public description PiperOrigin-RevId: 660963901

2024-07-18

fix!: Fix namespace for Ruby and PHP PiperOrigin-RevId: 653650485

2024-07-02

Update Eventarc schema PiperOrigin-RevId: 648737893

2024-06-27

Sync Cloud Scheduler schema (#606) PiperOrigin-RevId: 646979272 Co-authored-by: Copybara Bot <yoshi-code-bot@google.com>

2024-05-16

Update cloudscheduler.googleapis.com event schema in staging. (#602) PiperOrigin-RevId: 630464954 Co-authored-by: Copybara Bot <yoshi-code-bot@google.com>

2024-04-02

Add clouddeploy.googleapis.com events (#600) PiperOrigin-RevId: 609411296 Co-authored-by: Copybara Bot <yoshi-code-bot@google.com>

2024-03-07

batch.googleapis.com events schema (#599) PiperOrigin-RevId: 607685778 Co-authored-by: Copybara Bot <yoshi-code-bot@google.com>

2024-03-05

speech events schema (#596) PiperOrigin-RevId: 612922937 Co-authored-by: Copybara Bot <yoshi-code-bot@google.com>

2023-12-11

Add support for new event types that contains authentication context as an attribute extension. (#590) PiperOrigin-RevId: 586683237 Co-authored-by: Copybara Bot <yoshi-code-bot@google.com>

2023-07-07

fix: Correct namespaces for AlloyDB and GkeHub (#546) PiperOrigin-RevId: 544082663 Co-authored-by: Copybara Bot <yoshi-code-bot@google.com> Co-authored-by: Daniel Azuma <dazuma@gmail.com>

2023-07-04

fix: change display name for alloydb.googleapis.com and dataflow.googleapis.com (#543) PiperOrigin-RevId: 540973415 Co-authored-by: Copybara Bot <yoshi-code-bot@google.com>

2023-06-15

feat: new Network Management event types added (#539) PiperOrigin-RevId: 539981762 Co-authored-by: Copybara Bot <yoshi-code-bot@google.com>

fix: update GKE Hub event type to match API (#536) PiperOrigin-RevId: 540361708 Co-authored-by: Copybara Bot <yoshi-code-bot@google.com>

2023-06-14

Add Cloud AI Platform Notebooks event schema (#533) PiperOrigin-RevId: 540281258 Co-authored-by: Copybara Bot <yoshi-code-bot@google.com>

2023-06-06

Add Firestore event schema for Datastore mode (#527) PiperOrigin-RevId: 537979409 Co-authored-by: Copybara Bot <yoshi-code-bot@google.com>

2023-06-05

Update Firestore schema license (#525) PiperOrigin-RevId: 537950847 Co-authored-by: Copybara Bot <yoshi-code-bot@google.com>

2023-06-02

GKE Hub schemas (#519) PiperOrigin-RevId: 537334082 Co-authored-by: Copybara Bot <yoshi-code-bot@google.com>

2023-05-30

Update networkconnectivity and vmmigration events schemas (#517) PiperOrigin-RevId: 536472310 Co-authored-by: Copybara Bot <yoshi-code-bot@google.com>

2023-05-25

Update direct events schemas (#515) PiperOrigin-RevId: 534485735 Co-authored-by: Copybara Bot <yoshi-code-bot@google.com>

2023-05-16

Update direct events schemas (#511) PiperOrigin-RevId: 532472251 Co-authored-by: Copybara Bot <yoshi-code-bot@google.com>

2023-05-04

Add missing CloudEvent proto extensions (#507) PiperOrigin-RevId: 528535738 Co-authored-by: Copybara Bot <yoshi-code-bot@google.com>

2023-04-18

fix: Fix Ruby and PHP namespaces (#499) PiperOrigin-RevId: 522709585 Co-authored-by: Copybara Bot <yoshi-code-bot@google.com>

2023-04-06

Update Eventarc event schema (#497) PiperOrigin-RevId: 522336234 Co-authored-by: Copybara Bot <yoshi-code-bot@google.com>

2023-03-22

Add Cloud Dataflow event types (#493) PiperOrigin-RevId: 518554204 Co-authored-by: Copybara Bot <yoshi-code-bot@google.com>

2023-02-03

fix: Fix C# namespaces (#483) PiperOrigin-RevId: 506569363 Co-authored-by: Copybara Bot <yoshi-code-bot@google.com>

2023-01-05

chore: add go_package to third_party/.../monitored_resource (#461) This change allows using monitoring_resource as a proto dependency in Go without customizing Go import path mappings in the build process.

2022-12-16

Update direct event schemas (#459) PiperOrigin-RevId: 495864985 Co-authored-by: Copybara Bot <yoshi-code-bot@google.com>

2022-12-05

Update direct events schemas (#452) PiperOrigin-RevId: 492498768 Co-authored-by: Copybara Bot <yoshi-code-bot@google.com>

2022-11-28

Use java_multiple_files = true in CloudEvent proto. (#450) PiperOrigin-RevId: 490331830 Co-authored-by: Copybara Bot <yoshi-code-bot@google.com>

2022-09-14

Add CrashlyticsMissingSymbolsPayload to Cloud Eventarc API. (#403) PiperOrigin-RevId: 474378678 Co-authored-by: Copybara Bot <yoshi-code-bot@google.com>

Publish Cloud IoT schemas (#401) PiperOrigin-RevId: 474370979 Co-authored-by: Copybara Bot <yoshi-code-bot@google.com>

2022-09-08

Add FireperfThresholdAlertPayload. (#392) PiperOrigin-RevId: 470094233 Co-authored-by: Copybara Bot <yoshi-code-bot@google.com>

2022-08-25

simplify payload (#389) PiperOrigin-RevId: 469798073 Co-authored-by: Copybara Bot <yoshi-code-bot@google.com>

2022-08-12

Add feedback_console_uri to AppDistroInAppFeedbackPayload and clarify fast expiry of screenshot_uris. (#384) PiperOrigin-RevId: 467202442 Co-authored-by: Copybara Bot <yoshi-code-bot@google.com>

2022-07-28

Update comment for the LogEntryData AuthenticationInfo.principal_email to better reflect when the field may be redacted. (#379) PiperOrigin-RevId: 463889870 Co-authored-by: Copybara Bot <yoshi-code-bot@google.com>

2022-07-22

Sanitize service catalog and remove bad methods PiperOrigin-RevId: 462667787

2022-07-08

Fix comment. PiperOrigin-RevId: 459795963

2022-06-29

Add AppDistroInAppFeedbackPayload. PiperOrigin-RevId: 457989483

2022-05-16

[Copybara] Update with new internal changes from Piper (#356) * Fix service name for sts.googleapis.com PiperOrigin-RevId: 438060033 * Update service catalog for April 6th, 2022. PiperOrigin-RevId: 439893223 * Add CloudEvent Extension Attributes in RTDB schema. PiperOrigin-RevId: 448498649 * Fixing minor typos in the comments for FireAlerts schema (originally from https://github.com/googleapis/google-cloudevents/pull/350) PiperOrigin-RevId: 448608696 Co-authored-by: Copybara Bot <yoshi-code-bot@google.com>

2022-05-13

Fixing minor typos in comments (#350) Fixing minor typos in the comments.

2022-02-17

[Copybara] Support LogSplit within Cloud Audit Logs log entry events (#323) PiperOrigin-RevId: 424671554 Co-authored-by: Copybara Bot <yoshi-code-bot@google.com>

2022-02-02

[Copybara] Add protos for Firebase Alerts payload details (#316) * Add protos for Firebase Alerts payload details PiperOrigin-RevId: 422598251 * Fix LICENSE header PiperOrigin-RevId: 424671554 Co-authored-by: Copybara Bot <yoshi-code-bot@google.com> Co-authored-by: Marc Gomez <marc.gomez.vidal@gmail.com>

2021-12-14

Internal change PiperOrigin-RevId: 409994579

Fix import in the CloudEvent Firebase Alerts schema PiperOrigin-RevId: 415604627

2021-11-18

[Copybara] Update with new internal changes from Piper (#299) * feat: Add proto annotations for extension attributes. The `cloud_event_extension_attribute` annotation describes the attribute within events.proto, including the name, description and optional camel-cased name to aid tooling. The `cloud_event_extension_name` annotation indicates that Eventarc will (sometimes conditionally) include the specified extension attribute for the given event. Purpose of this change: - Collect as much information about an event in these protos, as a single source of truth - Enable tooling to make these extension attributes easier for customers to find. See https://github.com/googleapis/google-cloudevents-dotnet/pull/62 as an example PiperOrigin-RevId: 379672582 * docs: Remove TODO from Firestore event payload comment. PiperOrigin-RevId: 379709462 * Update to service catalog. PiperOrigin-RevId: 381051093 * Update to service catalog. PiperOrigin-RevId: 383638369 * docs: update readme catalog Signed-off-by: Grant Timmerman <timmerman+devrel@google.com> * Update service catalogs PiperOrigin-RevId: 387121524 * Revert "Update service catalogs" This reverts commit 0266aac177401fe5eb6e0f51218d14d767709454. This is to address the problem where 0266aac removes the CAL proto. This commit reverts that change. Later I will add a new CL that updates the service catalog. * Update to service catalog. PiperOrigin-RevId: 391849235 * Update Service Catalog on Sept 27, 2021 PiperOrigin-RevId: 399304046 * Remove invalid method names from service catalog. PiperOrigin-RevId: 401831500 * Update Service Catalog PiperOrigin-RevId: 403148687 * Update Service Catalog on Oct 29, 2021 PiperOrigin-RevId: 406397501 * Update Service Catalog with missing methodName PiperOrigin-RevId: 406825642 * Add matrix_id field to CloudEvent payload for Firebase Test Lab PiperOrigin-RevId: 409185529 * Update Service Catalog on November 15, 2021 PiperOrigin-RevId: 409994579 Co-authored-by: Copybara Bot <yoshi-code-bot@google.com> Co-authored-by: Jon Skeet <jonskeet@google.com> Co-authored-by: Grant Timmerman <744973+grant@users.noreply.github.com> Co-authored-by: Grant Timmerman <timmerman+devrel@google.com> Co-authored-by: Averi Kitsch <akitsch@google.com>

2021-09-27

[Copybara] Update with new internal changes from Piper (#266) * feat: Add proto annotations for extension attributes. The `cloud_event_extension_attribute` annotation describes the attribute within events.proto, including the name, description and optional camel-cased name to aid tooling. The `cloud_event_extension_name` annotation indicates that Eventarc will (sometimes conditionally) include the specified extension attribute for the given event. Purpose of this change: - Collect as much information about an event in these protos, as a single source of truth - Enable tooling to make these extension attributes easier for customers to find. See https://github.com/googleapis/google-cloudevents-dotnet/pull/62 as an example PiperOrigin-RevId: 379672582 * docs: Remove TODO from Firestore event payload comment. PiperOrigin-RevId: 379709462 * Update to service catalog. PiperOrigin-RevId: 381051093 * Update to service catalog. PiperOrigin-RevId: 383638369 * docs: update readme catalog Signed-off-by: Grant Timmerman <timmerman+devrel@google.com> * Update service catalogs PiperOrigin-RevId: 387121524 * Revert "Update service catalogs" This reverts commit 0266aac177401fe5eb6e0f51218d14d767709454. This is to address the problem where 0266aac removes the CAL proto. This commit reverts that change. Later I will add a new CL that updates the service catalog. * Update to service catalog. PiperOrigin-RevId: 391849235 * Update Service Catalog on Sept 27, 2021 PiperOrigin-RevId: 399304046 Co-authored-by: Copybara Bot <yoshi-code-bot@google.com> Co-authored-by: Jon Skeet <jonskeet@google.com> Co-authored-by: Grant Timmerman <744973+grant@users.noreply.github.com> Co-authored-by: Grant Timmerman <timmerman+devrel@google.com> Co-authored-by: Jay Shi <jayshi@google.com> Co-authored-by: Averi Kitsch <akitsch@google.com>

2021-06-16

docs: Remove TODO from Firestore event payload comment. PiperOrigin-RevId: 379709462

feat: Add proto annotations for extension attributes. The `cloud_event_extension_attribute` annotation describes the attribute within events.proto, including the name, description and optional camel-cased name to aid tooling. The `cloud_event_extension_name` annotation indicates that Eventarc will (sometimes conditionally) include the specified extension attribute for the given event. Purpose of this change: - Collect as much information about an event in these protos, as a single source of truth - Enable tooling to make these extension attributes easier for customers to find. See https://github.com/googleapis/google-cloudevents-dotnet/pull/62 as an example PiperOrigin-RevId: 379672582

2021-05-20

Firebase Remote Config Cloud Event schema PiperOrigin-RevId: 374903489

2021-05-06

Firebase Remote Config Cloud Event schema PiperOrigin-RevId: 372427118

2021-04-21

feat: Add ordering_key to PubsubMessage PiperOrigin-RevId: 369245730

2021-04-19

feat: Add ordering_key to PubsubMessage PiperOrigin-RevId: 369245730

2021-04-12

docs: updates firestore proto docs PiperOrigin-RevId: 368042968

2021-03-18

docs: update deprecation description for audit logs field PiperOrigin-RevId: 363664454

Manually update service catalog. PiperOrigin-RevId: 359176704

2021-02-22

fix: formats proto files (#167) PiperOrigin-RevId: 358888966 Co-authored-by: Copybara Bot <yoshi-code-bot@google.com>

2021-02-17

Internal change PiperOrigin-RevId: 357804159

2021-02-09

feat: Add publish_time to PubsubMessage Fixes #151

feat!: Rename fields in Firebase auth UserMetadata message This allows them to conform with our API conventions better. Functions Frameworks will need to perform appropriate conversions.

2020-11-30

fix: standardize data proto descriptions (#120) Signed-off-by: Grant Timmerman <timmerman+devrel@google.com>

2020-11-17

Specify the product in protos directly At this point, the protos are the true single source of truth for all the information we need. This is specified as a file-based option as we should never have multiple events for different products in the same proto file, and it would be annoying (and brittle) to specify the same product name separately in each event

2020-08-26

Fix Firebase event types (When the Firebase events are raised in Cloud Run, we'll be able to validate this, but until then it basically needs careful manual review. I wasn't careful enough when creating the initial PR...)

fix: Move the CloudBuild events under google.events.cloud.cloudbuild This makes the proto structure match the event type. (The duplication of "cloud" in the name has been discussed separately.)

2020-08-21

Wrap Cloud Audit Log event data in a log entry, to match reality on Cloud Run It's not entirely obvious which fields *should* be included in LogEntry. They broadly fall into three categories: Seen in examples, so included: - log_name - resource - proto_payload - insert_id - timestamp - receive_timestamp - severity Not seen in examples, but included as likely to be feasible: - trace - span_id Not seen in examples, and not included as I don't expect to see them: - text_payload - json_payload - http_request - labels - trace_sampled - source_location Before merging this, we should try to find out more information as to whether my guesses are correct. Compatibility note: I've made proto_payload an AuditLog value, which is compatible with the JSON serialized form of a LogEntry, but would *not* be compatible with the binary serialized form, which would have an Any value instead. If the eventing infrastructure wants to support protobuf binary serialization in the future, we'd probably need to introduce a new CloudEvent type for Cloud Audit Logs for that purpose. The alternative is to make this an Any (in the same way it is in the original proto) - which makes it significantly harder to access the AuditLog data which is the genuinely useful part.

Add google.api.MonitoredResource to third_party This is a greatly-reduced version of the original proto file, to avoid gaining other, unnecessary, dependencies.

2020-08-18

feat: CloudBuild event type (#40)

2020-08-17

Fix duplicated comment line

Expand the auth data for Firebase These fields need validating: I haven't seen them in my testing, but that's only been with simple email users.

Fix: Storage object improvements - Media/self link comments were the wrong way round - Add the "kind" field for completeness - it will always have the same value, but it *is* part of the REST resource model I have *not* included custom_time (despite it being in the Discovery doc) as I believe aspects of this are still in flux.

2020-08-11

Update AuditLogData based on googleapis This reflects the changes in the [googleapis commit](https://github.com/googleapis/googleapis/commit/40292fc8f271f3b8708f9c91c85d7240200893a6). Fixes most of the discrepancies noted in #43.

2020-08-07

Remove "old" Firebase events that will be replaced in later commits

Add Firebase RTDB CloudEvent schema

Add Firebase RemoteConfig CloudEvent schema Note: the CloudEvent type of "google.firebase.remoteconfig.remoteConfig.v1.updated" is a little odd and could do with discussion: - The "remoteconfig" part mirrors the proto package (as part of "firebase.remoteconfig" which is the product part) - The "remoteConfig" part is the resource name An alternative could be "google.firebase.remoteconfig.config.v1.updated" - so changing the resource part to just "config". Other suggestions very welcome.

Add Firebase Auth CloudEvent schema.

Add Firebase Analytics CloudEvent schema

Improve event message names I've kept AnalyticsLogWrittenEvent using the "Analytics" prefix as "log" could refer to anything, whereas UserCreated and UserCreated feel reasonably fully-qualified already. (The fact that there's a judgement call involved makes it hard to do this in a consistent but scalable manner. Happy to hear arguments for alternatives.)

Remove "wildcards" from Firestore document event data Internal discussions suggest this shouldn't be part of the event data. (It isn't part of the payload in GCF events; it's provided as a separate field in the root of the event body.) Client libraries can provide manually-written code to parse document names instead. Philosophically, this isn't part of the underlying event - it depends on the event subscription (which contains the resource template being used).

2020-07-06

Use a smaller extension field number for the cloud_event_type While the field number here *should* be valid, it at least causes problems in C#. I'll investigate whether this is a Google.Protobuf bug separately, but it does no harm to use a smaller number here.

Update Firestore event data proto to match internal field ordering This doesn't affect the JSON representation at all, but we might as well match internal proto field numbers where possible - it may have advantages in the future if we want to deliver proto binary representations of events.

Fix Firebase event types (These are deliberately not in a "cloud" directory, and so "cloud" shouldn't be in the event type.)

2020-07-01

Rename scheduler data message (#19)

2020-06-26

Change the Storage event_based_hold field to bool It's a BoolWrapper in the API to allow the distinction between "false", "true" and "unset" for the purpose of inheriting values from the bucket on object creation. This is unnecessary for event consumption. Fixes #6.

2020-06-25

Split events and data into separate protos This will allow us to generate only the data protos for client libraries

Fix the extension number for cloud_event_type

2020-06-24

Fix unused import warnings (This isn't strictly necessary, but it would be nice to keep the protos warning-free.)

Fix PubSub proto (message rename was incomplete) Will file an issue to create a Travis build that validates the protos.

2020-06-23

Add the "wrapper" around the PubSub message This corresponds to the JSON received for push notifications. In GCF events, there is no indication of the subscription; only the message is received as the event data. This means we cannot convert from the GCF format to the CloudEvent format.

Make storage crc32c hash a string

Remove execution time from scheduler schema

2020-06-22

Add fields which are in existing JSON, but not the API proto The field numbers are intended to be high enough to avoid conflicts with new API fields. Note that "kind" is not included here, as it's not expected to be useful.

2020-06-18

Introduce conventions for event and data messages

Adjust event types for pubsub and CAL

Add cloud scheduler event initial data schema

2020-06-15

First pass at CloudEvent proto messages (Note that this is intended to be enough to get us started; it is neither complete nor set in stone. See the stability warning in the top-level README.)

Introduce the third_party/googleapis directory All event protos should be able to compile with `protoc` adding only `third_party/googleapis` and the core protobuf package messages (in `google.protobuf`) for dependencies.