Skip to content

[IOCOM-2383]Remove push notifications rollout logic #1223

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

lucamancosu
Copy link
Collaborator

@lucamancosu lucamancosu commented Jun 10, 2025

Remove the temporary logic introduced with this PR.

Motivation and Context

The logic for the migration is no longer needed. The "old" logic is going to point directly to the new queue

How Has This Been Tested?

Screenshots (if appropriate):

Types of changes

  • Chore (nothing changes by a user perspective)
  • Bug fix (non-breaking change which fixes an issue)
  • New feature (non-breaking change which adds functionality)
  • Breaking change (fix or feature that would cause existing functionality to not work as expected)

Checklist:

  • My change requires a change to the documentation.
  • I have updated the documentation accordingly.

Copy link
Contributor

github-actions bot commented Jun 10, 2025

Jira Pull Request Link

This Pull Request refers to the following Jira issue IOCOM-2383

Copy link

@lucamancosu lucamancosu changed the title Remove tmp push notifications rollout logic [IOCOM-2383]Remove tmp push notifications rollout logic Jun 10, 2025
@lucamancosu lucamancosu changed the title [IOCOM-2383]Remove tmp push notifications rollout logic [IOCOM-2383]Remove push notifications rollout logic Jun 11, 2025
@lucamancosu lucamancosu marked this pull request as ready for review June 11, 2025 08:09
@lucamancosu lucamancosu requested a review from a team as a code owner June 11, 2025 08:09
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants