DEVEXP-912: snippets migration

[JPPortier]

No description provided.

[asein-sinch]

Although the other getting started insists and the fact the number will be rented and configured, in this one, the outcome will be the same, but we don't explain the SMS configuration part.

[JPPortier]

Right (this is coming from current snippet implementation https://developers.sinch.com/docs/numbers/getting-started/java-sdk/rentany/#rent-the-first-available-number-using-the-java-sdk)

@alex-sberna Regarding this getting started title and content should highlight
What is your opinion ?

• remove the configuration part ?
• improve the comment to highlight the configuration ?
• ?

[alex-sberna]

For the rent any, I think it is important to highlight that you are renting and configuring the number in the same call, so improving the comment would be good.

[JPPortier]

Done : b1e7ca9

[asein-sinch]

Approved, waiting for Alex's feedback

[samwil-sinch]

Successfully sent SMS using SMS API and Conversation API. However, I needed to manually setConversationRegion to ConversationRegion.EU; we may want to include a function that allows us to define the region in the config.properties file (in the same way we can set SMS_REGION).

Haven't tested/can't receive SMS because of ngrok restriction.

[alex-sberna]

I just tested handling an incoming message with SMS, which I now realize already existed and isn't part of this PR, but one thing I ran into was the validation/authorization of the callback URL, with the web secret. I think for a getting started/quickstart that that should be commented out by default, rather than having a user needing to comment it out. If someone is just starting and testing things out, they very likely won't bother contacting their account manager to get a secret added in order for it to work.

[JPPortier]

Successfully sent SMS using SMS API and Conversation API. However, I needed to manually setConversationRegion to ConversationRegion.EU; we may want to include a function that allows us to define the region in the config.properties file (in the same way we can set SMS_REGION).

Done

[JPPortier]

I just tested handling an incoming message with SMS, which I now realize already existed and isn't part of this PR, but one thing I ran into was the validation/authorization of the callback URL, with the web secret. I think for a getting started/quickstart that that should be commented out by default, rather than having a user needing to comment it out. If someone is just starting and testing things out, they very likely won't bother contacting their account manager to get a secret added in order for it to work.

Done.
By default sources are not validating the webhooks but code still present (and not executed)

[alex-sberna]

LGTM