Skip to content
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

PIPRES-349: Update subscription action #859

Conversation

mandan2
Copy link
Contributor

@mandan2 mandan2 commented Dec 5, 2023

Removed subscription's logger as it was not implemented anyways. Planning to migrate common service into "shared" folder to prevent duplicates

@mandan2 mandan2 self-assigned this Dec 5, 2023
@mandan2 mandan2 force-pushed the PIPRES-349-subscription-carrier-data-provider branch from f665063 to faeb933 Compare December 11, 2023 09:33
Base automatically changed from PIPRES-349-subscription-carrier-data-provider to PIPRES-349-enable-subscription-carrier-change December 11, 2023 09:36
@mandan2 mandan2 force-pushed the PIPRES-349-update-subscription-action branch from 0796f21 to 66d7869 Compare December 11, 2023 09:37
@mandan2 mandan2 merged commit 6df37ad into PIPRES-349-enable-subscription-carrier-change Dec 11, 2023
5 checks passed
@mandan2 mandan2 deleted the PIPRES-349-update-subscription-action branch December 11, 2023 09:38
JevgenijVisockij pushed a commit that referenced this pull request May 14, 2024
* PIPRES-349: Subscription carrier data provider

* renamed service and added missing DTO

* fixed return type

* renamed service

* PIPRES-349: Update subscription action

* updated exception code
JevgenijVisockij pushed a commit that referenced this pull request May 14, 2024
* PIPRES-349: Subscription carrier data provider

* renamed service and added missing DTO

* fixed return type

* renamed service

* PIPRES-349: Update subscription action

* updated exception code
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