CLI Access to Solace Cloud instances

[mhilmen]

When using Solace Cloud for the RESTful Getting Started examples on the Solace website (https://dev.solace.com/samples/solace-samples-rest-messaging/publish-subscribe/), the instructions do not tell you that you need to use port 2222 to ssh into the Solace CLI, it tells you to use the default port, port 22.

Also, there is a reference to a "VMR load" which likely means something to those familiar with Solace, but anyone new to the product will not understand. Would be better to use a Solace Cloud or other more appropriate reference.

[Aaron Lee]

Hi Mike @mhilmen ..! Doing some cleanup on old GH Issues. Note that the REST Messaging tutorial has been completely overhauled by Giri @gvensan not too long ago. Take a look, I think it addresses all your concerns: https://tutorials.solace.dev/rest-messaging/publish-subscribe/

I'm going to go ahead and close this old Issue. Thanks!

[mhilmen]

Thanks, I will check it out. From: Aaron Lee ***@***.***> Date: Wednesday, April 20, 2022 at 3:16 AM To: SolaceSamples/solace-samples-rest-messaging ***@***.***> Cc: Michael Hilmen ***@***.***>, Mention ***@***.***> Subject: Re: [SolaceSamples/solace-samples-rest-messaging] CLI Access to Solace Cloud instances (#18) Warning – this email originated outside of Solace. Please think before you click or open any links or attachments. If this email is suspicious, report it to ***@***.***

…

________________________________ Hi Mike @mhilmen<https://github.com/mhilmen> ..! Doing some cleanup on old GH Issues. Note that the REST Messaging tutorial has been completely overhauled by Giri @gvensan<https://github.com/gvensan> not too long ago. Take a look, I think it addresses all your concerns: https://tutorials.solace.dev/rest-messaging/publish-subscribe/ I'm going to go ahead and close this old Issue. Thanks! — Reply to this email directly, view it on GitHub<#18 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AB7DLT2V44CE4PZQNSN2JSLVF7KQRANCNFSM4GPBOV5Q>. You are receiving this because you were mentioned.Message ID: ***@***.***>

________________________________ Confidentiality notice This e-mail message and any attachment hereto contain confidential information which may be privileged and which is intended for the exclusive use of its addressee(s). If you receive this message in error, please inform sender immediately and destroy any copy thereof. Furthermore, any disclosure, distribution or copying of this message and/or any attachment hereto without the consent of the sender is strictly prohibited. Thank you.