Clarification for initialEvent use in documentation

[bigludo7]

What type of PR is this?

Add one of the following kinds:

• documentation

What this PR does / why we need it:

Clarify behavior of subscription/event server regarding use of initialEvent
Clarify roaming country change behavior

Which issue(s) this PR fixes:

Fixes #222

Special notes for reviewers:

Adding @gmuratk as reviewer.

Changelog input

 release-note
device-reachability-status-subscriptions:
- update yaml documentation part for initialEvent
device-roaming-status-subscriptions:
- update yaml documentation part for initialEvent
- update yaml documentation part for initialEvent roaming country change behavior

Additional documentation

This section can be blank.

docs

[github-actions]

🦙 MegaLinter status: ✅ SUCCESS

Descriptor	Linter	Files	Fixed	Errors	Elapsed time
✅ ACTION	actionlint	2		0	0.02s
✅ OPENAPI	spectral	6		0	10.13s
✅ REPOSITORY	git_diff	yes		no	0.01s
✅ REPOSITORY	secretlint	yes		no	0.8s
✅ YAML	yamllint	6		0	1.28s

See detailed report in MegaLinter reports

MegaLinter is graciously provided by

[gmuratk]

minor typos in table header:
subscrived --> subscribed
event send --> event sent

[gmuratk]

minor typos in table header:
subscrived --> subscribed
event send --> event sent

[gmuratk]

event is 'sent'

[sachinvodafone]

I am afraid that table is not coming nicely on the swagger editor

[sachinvodafone]

I took some time to interpret the table. Can we add some more information like (not necessary if others are fine with existing information):

[akoshunyadi]

@bigludo7 only the new connected-network-type-subscriptions file is missing here, then we could merge it... 🙂

[bigludo7]

@akoshunyadi This is because I do not have in my branch and I'm not able te retreive it :(
Do you think we can merge this one and then I trigger a specific PR for connected-network-type-subscriptions ?

[akoshunyadi]

@bigludo7 sure we can do it.... but..is there a specific error when you want to update the branch?

[bigludo7]

@bigludo7 sure we can do it.... but..is there a specific error when you want to update the branch?

I would like to populate my branch with latest code but it trigger a PR to the project :(

[bigludo7]

@bigludo7 sure we can do it.... but..is there a specific error when you want to update the branch?

I would like to populate my branch with latest code but it triggers a PR to the project :(

[akoshunyadi]

that's weird, anyway then I review this one and the 3rd api will be done in a new PR

[akoshunyadi]

LGTM.
Just a comment: checking the reachability status subscriptions file... it doesn't really fit now the reachability retrieve API, which supports both data and sms at the same time. Do we need a change for that? Not for Spring25, for sure.

[bigludo7]

Thanks @akoshunyadi
Will merge it tomorrow and craft a new one for the last api.

Fair question. I tend to think this is less relevant for the subscription than for the 'direct' request but in same time have same behavior btw both API is more consistent.

Let's open an issue to gather team feedback.