[GH-ISSUE #2131] Support multiple Pub/Sub notification configurations #255

New issue

Open

opened 2026-03-03 12:09:27 +03:00 by kerem · 1 comment

kerem commented

2026-03-03 12:09:27 +03:00

Owner

Originally created by @lberrymage on GitHub (Feb 2, 2026).
Original GitHub issue: https://github.com/fsouza/fake-gcs-server/issues/2131

fake-gcs-server currently supports only a single Pub/Sub notification configuration, which is more limited than the multiple notification configurations supported by Google Cloud Storage. This means users cannot model certain system architectures with fake-gcs-server, namely, those which use multiple notification configurations (e.g., upload events in different buckets sending messages to different Pub/Sub topics).

Ideally, fake-gcs-server would support specifying multiple notification configurations on the command line so that users can use it for integration testing in these more complex system architectures.

A notification configuration has a well-defined model and is always attached to a specific bucket. Since buckets may not exist before fake-gcs-server starts, I think the best solution to handle nonexistent buckets would be to treat the bucket as a filter such that the configuration is treated as if it doesn't exist if the bucket it's attached to doesn't exist.

Originally created by @lberrymage on GitHub (Feb 2, 2026). Original GitHub issue: https://github.com/fsouza/fake-gcs-server/issues/2131 `fake-gcs-server` currently supports only a single Pub/Sub notification configuration, which is more limited than the [multiple notification configurations](https://docs.cloud.google.com/storage/docs/pubsub-notifications#notification-configs) supported by Google Cloud Storage. This means users cannot model certain system architectures with `fake-gcs-server`, namely, those which use multiple notification configurations (e.g., upload events in different buckets sending messages to different Pub/Sub topics). Ideally, `fake-gcs-server` would support specifying multiple notification configurations on the command line so that users can use it for integration testing in these more complex system architectures. A notification configuration has a [well-defined model](https://docs.cloud.google.com/storage/docs/json_api/v1/notifications) and is always attached to a specific bucket. Since buckets may not exist before `fake-gcs-server` starts, I think the best solution to handle nonexistent buckets would be to treat the bucket as a filter such that the configuration is treated as if it doesn't exist if the bucket it's attached to doesn't exist.

kerem commented

2026-03-03 12:09:28 +03:00

Author

Owner

@lberrymage commented on GitHub (Feb 4, 2026):

I've gotten this working in a local branch. I plan on making on a PR once I have the implementation cleaned up a little.

@lberrymage commented on GitHub (Feb 4, 2026): I've gotten this working in a local branch. I plan on making on a PR once I have the implementation cleaned up a little.