I've finally finished the opsdroid/opsdroid#1767, I've added a video so you can see how the logs look like without having to test locally.
Cadair I've also added a new formatter config so a user can choose a formatting string. I remember you mentioned that it would be good to allow a user to do this 👍️
I'm using Pycharm and a python venv with installed opsdroid.
Unfortunately my breakpoints don't stop at the skill script. ☹️
1 reply
That seems like a great Microsoft idea 😄
We were struggling with getting logs from azure because Microsoft decided to make one part of the storage url random 🤦♂️
Ajit D'Sa and I have been working on some DB updates. Updated MongoDB, added a postgres, but also we could update SQLite.
The main reason is this:
Skills should be allowed to specify which table they save to.
Right now, one opsdroid instance with one DB, two different skills will save into the same table/collection of the same db.
So we allow:
- setting default table name in DB
- depending on skill, allowing default table (or tables) name in skill config
- setting table name in the
putandgetfunctions as an optional kwarg.
I do not know how to write good tests for this. Is there a way to spin up a postgres instance on commit and run unit tests against it? Or decent mock modules available?
Awesome thanks! I'm excited to see this work happening.
I'm curious about the desire to have different tables/collections for each skill. I've always considered it a feature that the opsdroid memory object is accessible from any skill. Each skill can just choose a prefix for the key name if there are concerns about collision.
1 reply
pytest-docker to start a postgres database as part of the pytest fixtures.
1 reply
1 reply
