opsdroid / connector-ciscospark

📡 A Cisco Spark connector for opsdroid

An open source chat-ops bot framework

---

Quick Start • Documentation • Playground • Blog • Community

---

An open source chatbot framework written in Python. It is designed to be extendable, scalable and simple.

This framework is designed to take events from chat services and other sources and execute Python functions (skills) based on their contents. Those functions can be anything you like, from simple conversational responses to running complex tasks. The true power of this project is to act as a glue library to bring the multitude of natural language APIs, chat services and third-party APIs together.

See our full documentation to get started.

Contributors

This project exists thanks to all the people who contribute. [Contribute].

Backers

Thank you to all our backers! 🙏 [Become a backer]

Sponsors

Support this project by becoming a sponsor. Your logo will show up here with a link to your website. [Become a sponsor]

connector-ciscospark's Issues

Verify secret

When creating the webhook an optional secret can be passed.

I assume this means the messages can be verified against this secret somehow. So that should probably be implemented.

Fix some bugs to cisco spark and change the project name

Hi opsdroid team, cisco has renamed ciscospark to webexteams, and I found this repo not work with the latest version of opsdroid(0.14.1), so I fix some bugs and it work properly now, can you create a new project named webexteams and then I push the code to the new repo or I still push the bug fix to this repo

Handle error if webhook-url has not been set

The connector will error if the webhook-url config option has not been set. This should have some error handling.

Add response error handling

Currently the respond method has no error handling. This should be added.

Opsdroid seems to default to apiai parser, on by default?

My parser section from configuration.yaml is:

Parsers

parsers:

• name: regex
  enabled: true

- name: crontab

enabled: true

- name: apiai

access-token: "youraccesstoken"

min-score: 0.6

But the debug shows, that it is using apiai, but really it should be using regex?:

DEBUG opsdroid.core: Parsing input: vcc load info
DEBUG opsdroid.core: Processing parsers
DEBUG opsdroid.core: Checking apiai

Does not receive group messages

It appears that despite the bot being in multiple rooms the webhook only sends direct messages.

For local skill files, no-cache should the default config?

Not sure if caching for local skill files should be on by default as it is a bit confusing to not see changes to the skills being reflected in the functionality. I had to dig a bit to see that opsdroid was caching local files in ~/.opsdroid/modules. Totally makes sense for git repositories though where the lag would be a problem for quick parsing.

Make asynchronous

Currently the spark library runs synchronously, which means this connector will block when responding to messages.

All Cisco Spark library calls should be wrapped up asynchronously.

Debug logging doesn’t show message contents only headers

Debug logging - doesn’t show message being sent/received to/from the bot, only headers. In my debug trace it does seem to extract what to parse, but not the response from the skill returned to the bot:

DEBUG opsdroid.core: Parsing input: vcc load info
DEBUG opsdroid.core: Processing parsers
DEBUG opsdroid.core: Checking apiai

Trailing slash in webhook url causes error

The webhook url and path are not intelligently joined. Therefore if you leave a trailing slash in the webhook url you end up with a double slash in the url sent to spark, which causes it not to work.

The two halves of the url should be intelligently joined.

Improve cleaning up webhooks

Currently when opsdroid exits any webhooks that are created will be left in place. When opsdroid next starts it will clean up and old webhooks and create new ones.

This isn't ideal because:

• It cleans up all webhooks, even if they weren't created by opsdroid
• The Cisco api could end up trying to hit a decommissioned bot forever
• You might want multiple opsdroids connected (no idea why but you might)