"micro" subcommand not found about natscli

[ripienaar]

so it goes :) I fixed the confusing error message you showed though so thanks for the report regardless!

[ripienaar]

if you are using nightly you can do nightly-yyyymmdd as a tag

[ripienaar]

It be will be in the next release. Currently in nightly release in the synadia/nats-server:nightly container

[jplimack]

@ripienaar I deployed nats-server:nightly and compiled the latest nats-cli, but stuck here

./dist/nats_darwin_arm64/nats micro list 
nats: error: server request failed, ensure the account used has system privileges and appropriate permissions

any pointers on what I need to do next to authenticate this properly? I have auth disabled at the moment in my local dev cluster

[ripienaar]

That’s weird - it’s not a system account thing probsbly a error that’s handled incorrectly. I think it means no services are running.

[jplimack]

ive got a micro.service with 2 endpoints that is responding to requests, just unable to use nats-cli to see any status

[ripienaar]

OK, then its not in the same account or not up or not connected or similar. you can do nats req '$SRV.INFO' '{}' and should see no responses

[ripienaar]

The basic issue of moaning about system account is fixed in next nightly, but still the problem you're having is that no micro services are responding.

[jplimack]

nats req '$SRV.INFO' '{}'
07:48:36 Sending request on "$SRV.INFO"
07:48:36 Received with rtt 1.982083ms
{"name":"mytestmicroservice","id":"yMh1DDbTVHVtlvPtojNrqN","version":"0.0.1","type":"io.nats.micro.v1.info_response","description":"provides example nats micro.service for demo","subjects":["thething","thething.nounn.list"]}

I think I do have a micro.service listening, and it does respond when i publish at it

[ripienaar]

ok, so show nats micro ls --trace pls

[jplimack]

maybe all i had to do was get a good night's rest /shrug

 nats micro ls --trace                  
07:56:09 >>> $SRV.INFO: {}
{"name":"mytestmicroservice","id":"yMh1DDbTVHVtlvPtojNrqN","version":"0.0.1","type":"io.nats.micro.v1.info_response","description":"provides example nats micro.service for demo","subjects":["thething","thething.nounn.list"]}
07:56:09 === Received 1 responses
╭────────────────────────────────────────────────────────────────────────────────────────────╮
│                                     All Micro Services                                     │
├───────┬─────────┬────────────────────────┬─────────────────────────────────────────────────┤
│ Name  │ Version │ ID                     │ Description                                     │
├───────┼─────────┼────────────────────────┼─────────────────────────────────────────────────┤
│ mysvc │ 0.0.1   │ yMh1DDbTVHVtlvPtojNrqN │the desc │
╰───────┴─────────┴────────────────────────┴─────────────────────────────────────────────────╯

[jplimack]

thanks for your help! I'm really enjoying developing with nats and micro is really convenient

[jplimack]

@ripienaar do you publish the digests of the images? kubernetes wont know to pull the new image if it has the tag cached. I see you're using go-releaser, which can do a pre-release, any chance of tagging the nightlies?