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

Scope of SimSwap for Fall24 CAMARA Release #122

Closed
bigludo7 opened this issue Jul 9, 2024 · 0 comments · Fixed by #127
Closed

Scope of SimSwap for Fall24 CAMARA Release #122

bigludo7 opened this issue Jul 9, 2024 · 0 comments · Fixed by #127
Labels
Fall24 Fall 24 release preparation subproject management Indicating issues with subproject repository or release management process

Comments

@bigludo7
Copy link
Collaborator

bigludo7 commented Jul 9, 2024

This issue shall define which issues are within scope of APIs of the Sub Project for the Fall24 release and will be regularly updated based on the decision within the Sim Swap API meetings.
Note: this issue is only for sim_swap and not covering sim-swap-notification-subscription

Alignement with commonalities & icm

  • PhoneNumber pattern - clarification on optional "+" prefix (issue85)
  • Revisit defined errors (issue119)

Enhancement

  • Add API-Name (aka wild-card) as scope in the yaml (issue103)
  • Provide test definition (issue63)
  • Provide user stories(issue121)

Fixes

  • phone number instead of MSISDN to follow commonalities guidelines (issue116)
  • Make response properties "latestSimChange" and "swapped" required since they will always be returned (issue96)
@bigludo7 bigludo7 added subproject management Indicating issues with subproject repository or release management process Fall24 Fall 24 release preparation labels Jul 9, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Fall24 Fall 24 release preparation subproject management Indicating issues with subproject repository or release management process
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant