mage-os / mageos-async-events-gcp
mage-os/mageos-async-events-gcp
GCP event sinks for mage-os/mageos-async-events
MageOS Async Events GCP
GCP event sinks for mageos-async-events
Installation
composer require mage-os/mageos-async-events-gcp
Authenticating with Google Cloud Client Libraries
This module relies on Google's PHP Cloud Client Libraries. Each event sink uses a corresponding library to perform
requests to Google Cloud.
For more information about the client libraries, please see https://cloud.google.com/php/docs/reference
As per the Authentication Guide, the
recommended way to authenticate to the Google Cloud PHP library is to use Application Default Credentials (ADC),
which discovers your credentials automatically, based on the environment where your code is running.
Application Default Credentials (ADC) typically come in the form of a credential JSON file. This file can include
credentials for workload identity federation, workforce identity federation, or a service account key.
There are many ways to obtain an ADC, so you must review and choose a method that fits your use case.
[!IMPORTANT]
Service account keys can pose a security risk if not managed correctly. Whenever possible, opt for a more secure
alternative to service account keys.
To authenticate using different methods, refer to the following guides:
- Service Account Key: Service account key authentication
- Workload Identity Federation: Workload Identity Federation authentication
- Google Cloud Services: If your code is running on a supported Google Cloud service such as Compute Engine, you can authenticate by attaching a service account. Read more about Google Cloud services that support attaching a service account
- GKE or GKE Enterprise: Containerized authentication
GCP event sinks
Google Pub/Sub
Setup Application Default Credentials (ADC)
A Service Account with the Pub/Sub Publisher role is required so that the notifier can relay events into Google
Pub/Sub.
Under Stores -> Services -> Async Events GCP set the ADC Path.
[image: gcp-pubsub-config example]
Create a Pub/Sub Subscription
The following is an example to create a Pub/Sub subscription for the example.event
curl --location --request POST 'https://test.mageos.dev/rest/V1/async_event' \
--header 'Authorization: Bearer TOKEN' \
--header 'Content-Type: application/json' \
--data-raw '{
"asyncEvent": {
"event_name": "example.event",
"recipient_url": "Google Pub/Sub Topic",
"verification_token": "supersecret",
"metadata": "pubsub"
}
}'
No changelog yet
The vendor hasn't published a changelog. Tagged releases appear in the Versions tab.
Requires 3
| Package | Constraint |
|---|---|
| php | >=8.1 |
| mage-os/mageos-async-events | ^4.0 |
| google/cloud-pubsub | ^2.0 |
Compatibility
Each Magento release line is installed on its supported PHP versions, then the module is built (DI compilation + static-content deploy) and its unit and integration suites are run. The matrix shows the lines and PHP versions the module is confirmed to install and run on. Code-quality results further down (phpstan, phpcs, …) are reported separately and never affect compatibility.
Code Quality
Advisory checks against the module's source. Static analysis runs once across the whole module; PHPStan re-runs per Magento + PHP version because resolvable symbols differ between releases. These NEVER affect the Compatibility badge — a phpcs finding can't make a module incompatible.
Static analysis
Coding standards (phpcs), mess detection (phpmd), copy-pasted code (cpd), PHP cross-version compatibility, composer.json validity. Each runs once for the whole module.
PHPStan
Type-checks the module's PHP against a real Magento install at the configured gate level. Re-runs per Magento and PHP version because resolvable symbols differ between releases. Cell → details modal.
Tests
Unit and integration suites, run for each applicable Magento and PHP version. A test failure speaks to the module's behaviour, not its compatibility with a Magento line, so it is reported here separately and never reddens the compatibility matrix.
Unit tests
| Magento | PHP 8.2 | PHP 8.3 | PHP 8.4 | PHP 8.5 |
|---|---|---|---|---|
| 2.4.7 | N/A | N/A | ||
| 2.4.8 | N/A | N/A | ||
| 2.4.9 | N/A | N/A |
Integration tests
| Magento | PHP 8.2 | PHP 8.3 | PHP 8.4 | PHP 8.5 |
|---|---|---|---|---|
| 2.4.7 | N/A | N/A | ||
| 2.4.8 | N/A | N/A | ||
| 2.4.9 | N/A | N/A |
Security
Security checks run directly against the module: an audit of its declared dependencies for known vulnerabilities (composer audit) and a scan of its source for malware and web-shell signatures. Each runs once. A malware detection fails the version outright.
More from mage-os
View vendorCombine the power of LLM and domain knowledge to improve admin experience though a chatbot UI.
MageOS Newsletter Coupon Generator
Turn an existing module into recurring revenue.
If you already maintain a Magento 2 module on GitHub or GitLab, listing it on Packagento takes about five minutes. We mirror your tags, handle distribution signing, and route paid licenses through Stripe Connect, so you can keep shipping the way you already do.