hrynco/hrynco-notification-service
1
0
Fork 0
Code Issues Pull Requests 1 Actions Packages Projects Releases Wiki Activity

feat(push): add service-owned Firebase channels and delivery #28

Merged
agrynco merged 1 commits from feature/IT-1074-android-push into main 2026-10-24 12:32:22 +03:00
Conversation 0 Commits 1 Files Changed 105
+3838 -147
agrynco commented 2026-10-24 12:31:57 +03:00
Owner
Copy Link
Copy Source

Notification Service now owns Firebase channel credentials and exposes separate authorization and test-send actions. Push contracts and the worker support service-based FCM routing, persisted delivery outcomes, bounded retries and safe errors. Email channels reference the service catalog by ID, preserving links across renames; editors use compact layouts and the development migration command reads the existing local configuration.

Validation: Release solution build, 67 unit tests and 154 integration tests passed. Rider reported no errors in the inspected production classes. Owner verified real Firebase test notification display and tap-to-open on Samsung. This does not verify the separate Invemory data-only/outbox flow. Existing Microsoft.OpenApi 2.0.0 vulnerability warning remains.

Apply the three included migrations with the normal deployment chain. Legacy email names must resolve uniquely, including the approved StoreMate-Prod to Invemory-Prod alias. Credentials stay write-only in the private-network administration UI. No real credentials or recipient tokens are committed.

Scope is this repository only. The owner explicitly authorized the main-triggered production deployment and automatic Contracts publication. Invemory dependencies and remaining repositories are not delivered; IT-1074 stays open.

Ref: IT-1074

Notification Service now owns Firebase channel credentials and exposes separate authorization and test-send actions. Push contracts and the worker support service-based FCM routing, persisted delivery outcomes, bounded retries and safe errors. Email channels reference the service catalog by ID, preserving links across renames; editors use compact layouts and the development migration command reads the existing local configuration. Validation: Release solution build, 67 unit tests and 154 integration tests passed. Rider reported no errors in the inspected production classes. Owner verified real Firebase test notification display and tap-to-open on Samsung. This does not verify the separate Invemory data-only/outbox flow. Existing Microsoft.OpenApi 2.0.0 vulnerability warning remains. Apply the three included migrations with the normal deployment chain. Legacy email names must resolve uniquely, including the approved StoreMate-Prod to Invemory-Prod alias. Credentials stay write-only in the private-network administration UI. No real credentials or recipient tokens are committed. Scope is this repository only. The owner explicitly authorized the main-triggered production deployment and automatic Contracts publication. Invemory dependencies and remaining repositories are not delivered; IT-1074 stays open. Ref: IT-1074
agrynco added 1 commit 2026-10-24 12:31:58 +03:00
feat(push): add service-owned firebase channels and delivery 1631786ce2 
Add push contracts, provider delivery and channel diagnostics. Link email channels to services and document migration and validation.

Ref: IT-1074
agrynco merged commit d4ee8fc0c8 into main 2026-10-24 12:32:22 +03:00
Sign in to join this conversation.
Reviewers
No Reviewers
Labels
No items
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
agrynco (Anatolii Hrynchuk)
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: hrynco/hrynco-notification-service#28
Delete Branch "feature/IT-1074-android-push"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?