(#2314) Re-enable choria broker object and initialize natscli context

[skel84]

Summary

This PR re-enables choria broker object and ensures the embedded natscli config is initialized, so object-store operations work against the broker without a separate NATS instance.

Motivation

Needed for the ccm-hoist + choria-terraform workflow to upload bundles and data directly to the broker object store:

• https://github.com/skel84/ccm-hoist
• https://github.com/skel84/choria-terraform

Changes

• Remove object from the natscli command disable list.
• Initialize natscli config to avoid nil-context panics.

Testing

• Manual: choria broker object add/put/ls against broker object store; CCM agent pulled manifests + data from broker object store.

Issue

• Closes Re-enable choria broker object commands #2314

[ripienaar]

object was never enabled because, well, I am not that bullish on object but its ok for what CCM does so happy to enable.

I'll also land tonight support for HTTP instead of NATS Object Store for downloading manifests which might help.

Would love your thoughts on ccm :)

[ripienaar]

Also worth noting that ccm cant connect to choria broker, must be nats broker without Choria's auth changes - essentially you cant really say Choria Broker is a NATS Server since it speaks different auth

[ripienaar]

Failures here are due to certificates expiring, I'll fix that dont worry

[skel84]

I'm loving ccm so far! I really like the whole choria echosystem's philosophy, i find very unix-y, each tool does a job well, and i started playing around with it. At work, we might end up using puppet-hoist! I also created a ccm-hoist, and another repo with some terraform script to test the whole thing. Also I created a PR for ccm, not sure if it goes in the direction that you have in mind though

[ripienaar]

I'm loving ccm so far! I really like the whole choria echosystem's philosophy, i find very unix-y, each tool does a job well, and i started playing around with it. At work, we might end up using puppet-hoist! I also created a ccm-hoist, and another repo with some terraform script to test the whole thing. Also I created a PR for ccm, not sure if it goes in the direction that you have in mind though

Hoist will benefit a bunch from CCM features and I want to formalise the service registry concept a bit more so that a ccm file resource can generate - lets say prometheus - config from the service registry.

This way hoist can register services, annotate prom urls and a simple ccm ensure file ... can generate your prometheus targets file from cron :)