michalslowikowski00 commented on pull request #91:
URL: https://github.com/apache/kibble/pull/91#issuecomment-726838070


   > Hi, really sorry about the delay. I was able to completely migrate the 
setup workflow to be implemented with `click`. I am running into a minor error 
while running `create_es_index` which I don't believe has anything to do with 
the new cli implementation. Was wondering if I could get some assistance with 
figuring out the issue as I am a bit new to ElasticSearch 😅?
   > 
   > Seems I am receiving a connection error when calling elasticsearch:
   > 
   > ```shell
   > elasticsearch.exceptions.ConnectionError: 
ConnectionError(<urllib3.connection.HTTPConnection object at 0x111424fd0>: 
Failed to establish a new connection: [Errno 8] nodename nor servname provided, 
or not known) caused by: NewConnectionError(<urllib3.connection.HTTPConnection 
object at 0x111424fd0>: Failed to establish a new connection: [Errno 8] 
nodename nor servname provided, or not known)
   > ```
   > 
   > The actual cli commands and arguments are working now though 👍
   > 
   > ```shell
   > $ kibble version
   > 1.0.0dev
   > $ kibble setup --help
   > Usage: kibble setup [OPTIONS]
   > 
   > Options:
   >   -u, --uri TEXT          Pre-defined connection uri for ElasticSearch.
   >   -d, --dbname TEXT       Pre-defined Database prefix.
   >   -s, --shards TEXT       Predefined number of ES shards.
   >   -r, --replicas TEXT     Predefined number of replicas for ES.
   >   -m, --mailhost TEXT     Pre-defined mail server host.
   >   -a, --autoadmin TEXT    Generate generic admin account.
   >   -k, --skiponexist TEXT  Skip DB creation if DBs exist.
   >   --help                  Show this message and exit.
   > ```
   
   Easy, it's open source. :)


----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

For queries about this service, please contact Infrastructure at:
[email protected]


Reply via email to