[HZ-5349] Fixed Hazelcast Cloud sample

[yuce]

No description provided.

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 93.47%. Comparing base (90627dd) to head (c9b8bb9).
⚠️ Report is 8 commits behind head on master.

Additional details and impacted files

@@            Coverage Diff             @@
##           master    #1578      +/-   ##
==========================================
+ Coverage   93.45%   93.47%   +0.02%     
==========================================
  Files         466      466              
  Lines       16644    16645       +1     
  Branches     1353     1353              
==========================================
+ Hits        15554    15559       +5     
+ Misses        797      792       -5     
- Partials      293      294       +1     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

[ihsandemir]

do you have a sample run that you can share this worked as expected?

[yuce]

@ihsandemir I ran the code on local with starting the cluster using CLC.
These are the steps I used:

$ clc  cloud login
$ clc cloud create-cluster --name test1
$ cat `clc home configs test1 config.json`  # to see cloud cluster credentials
$ # update code_samples/hazelcast_cloud_discovery.js with cloud credentials
$ make build
$ node code_samples/hazelcast_cloud_discovery.js
$ clc cloud stop-cluster test1

[ihsandemir]

Instruction on how to setup cloud cluster etc. as mentioned in #1578 (comment) can be documented at the README.

[alaktionov]

Verified the code sample against my 5.6.0 cluster in Hazelcast Cloud (dev environment):

alaktionov@HZLCST-MBP-10 hazelcast-cloud-nodejs-sample-client-qvk1qn9s % npm run client
[DefaultLogger] INFO at LifecycleService: HazelcastClient is STARTING
[DefaultLogger] INFO at LifecycleService: HazelcastClient is STARTED
[DefaultLogger] INFO at ConnectionManager: Trying to connect to 10.0.43.129:30000
[DefaultLogger] INFO at LifecycleService: HazelcastClient is CONNECTED
[DefaultLogger] INFO at ConnectionManager: Authenticated with server 10.0.43.129:30000:951cfb7b-6118-4796-bc0a-f2a4e51825d2, server version: 5.6.0, local address: 10.252.252.170:64146
[DefaultLogger] INFO at ClusterService:

Members [3] {
	Member [10.0.50.115]:30000 - 71c107dc-365e-43a9-bdf3-b864d6f720b1
	Member [10.0.44.132]:30000 - fa585b56-08a2-484f-bd33-8238d47d265f
	Member [10.0.43.129]:30000 - 951cfb7b-6118-4796-bc0a-f2a4e51825d2
}

[DefaultLogger] INFO at ConnectionManager: Authenticated with server 10.0.50.115:30000:71c107dc-365e-43a9-bdf3-b864d6f720b1, server version: 5.6.0, local address: 10.252.252.170:64147
[DefaultLogger] INFO at ConnectionManager: Authenticated with server 10.0.44.132:30000:fa585b56-08a2-484f-bd33-8238d47d265f, server version: 5.6.0, local address: 10.252.252.170:64148
[DefaultLogger] INFO at Statistics: Client statistics is enabled with period 5 seconds.
Connection Successful!
value:  world
[DefaultLogger] INFO at LifecycleService: HazelcastClient is SHUTTING_DOWN
[DefaultLogger] INFO at ConnectionManager: Removed connection to endpoint: 10.0.43.129:30000:951cfb7b-6118-4796-bc0a-f2a4e51825d2, connection: Connection{alive=false, connectionId=0, remoteAddress=10.0.43.129:30000}
[DefaultLogger] INFO at ConnectionManager: Removed connection to endpoint: 10.0.50.115:30000:71c107dc-365e-43a9-bdf3-b864d6f720b1, connection: Connection{alive=false, connectionId=1, remoteAddress=10.0.50.115:30000}
[DefaultLogger] INFO at ConnectionManager: Removed connection to endpoint: 10.0.44.132:30000:fa585b56-08a2-484f-bd33-8238d47d265f, connection: Connection{alive=false, connectionId=2, remoteAddress=10.0.44.132:30000}
[DefaultLogger] INFO at LifecycleService: HazelcastClient is DISCONNECTED
[DefaultLogger] INFO at LifecycleService: HazelcastClient is SHUTDOWN