cesarbr / knot-cloud Goto Github PK

As a developer, I want to be able to disable a gateway I own, so that I can restore it later in a different hardware.

The KNoT CLI init command is shown in the help menu but when running it nothing happens. The weird thing about it is that if the filename and the command name are differente it works correctly. So, I'd suggest investigating if some bug was introduced when the other cloud commands were added to the CLI or if there is a bug in the yargs package.

As a developer, I want to disable an application from managing things, i.e. create, update, remove and search them.

DoD:

• Disable apps to create things on protocol adapter;
• Add an option to app creation card on UI in order to enable the developer setup this ability;
• When listing the apps on UI, we must see if the app is able to manage things (it could be through a property on device).

As an application developer, I want to have resources that help me use KNoT Cloud, so that I can easily create my solutions with the platform.

DoD:

• Developers have resources to help them deploy KNoT Cloud
• Developers have resources to explain each configuration item it might find while deploying KNoT Cloud
• Developers have resources to help them create applications: how to generate credentials and how to use credentials to perform KNoT operations
• Developers have resources to help them create gateways: how to generate credentials, how to connect KNoT Gateway to KNoT Cloud
• Developers have resources to help them create devices: how to generate credentials, how to use credentials to perform KNoT device operations.

As an application developer, I want to have an automated way to bring a KNoT Cloud stack up, so that I can easily work with KNoT.

DoD:

• Stack can be brought automatically with one or a few commands
• No external tools (such as openssl) except tools provided by KNoT or docker itself (or some other deployment related tool, e.g. Ansible) must be used.
• No manual edit of files must be required.

As a developer, I want to have a tool that I can use to operate on the KNoT Cloud, so that I don't need to write my own client to interact with it.

DoD:

• A tool that can be download/compiled/installed.
• Must require only that I have a user created on the cloud.
• Must provide all the operations provided by the protocol adapter and support all the device types (gateway, app, thing).

When trying to deploy the stack I noticed the traefik couldn't be executed because its configuration parameters changed in the latest version (v2.0).

https://docs.traefik.io/migration/v1-to-v2/

As a developer, I want to be able to develop a KNoT solution using my platform of choice, so that I don't need to create another environment only for this purpose.

DoD:

• Support development on Mac OS X
• Support development on Ubuntu, Arch Linux, ?
• Support development on Windows 10 (desired)

As an application developer, I want to be able to write my applications using Python so that I don't need to change my development environment.

DoD:

• Be able to interact with WebSocket protocol adapter using Python
• Be able to interact with authenticator service using Python
• Be able to interact with storage service using Python
• Be able to fetch the libraries in a public package repository

As a developer, I want to have an automated way to build and test the services when a new tag is released, and publish to NPM if it's a library. Moreover, I want to be notified if anything fails.

DoD:

• Investigate CI/CD automation tools: TravisCI, CircleCI and Jenkins;
• Add building and testing steps;
• Add publishing to NPM;
• Send notifications to slack;
• Generate CHANGELOG files;

During testing with the knot device, I found a problem with the thing-token authentication. The knot is confirming the device authentication message without re-verifying the thing token. My test:
My device sends the registration message and receives the confirmation along with a think token, then an authentication request is sent to the knot without informing the thing token, and the confirmation is received without errors. In the image the babeltower receives an authentication message without any token and confirms normally.