drogue-cloud
drogue-cloud copied to clipboard
drogue-iot
Cloud Native IoT
As far as I can see, the whoami endpoint is not used anymore in the console as it pull the username from the oauth token claim. In the case where...
Currently the overview page in the console lists all kind of information. Without giving any information what this means. We should create a nice (visually appealing and informational) page which...
https://docs.github.com/en/codespaces/setting-up-your-project-for-codespaces/adding-a-dev-container-configuration/introduction-to-dev-containers
This is the initial implementation for https://github.com/drogue-iot/rfcs/pull/19 This add a few new permissions and associated roles. It also add scopes to personal access tokens. What is still TODO : -...
Some other drogue crates are re-exported multiple times . What I've found so far : `drogue_bazaar::auth::UserInformation` - service-api/src/auth/user/mod.rs - service-common/src/auth/mod.rs `drogue_bazaar::auth::authorization::Authorizer` : - service-common/src/auth/mod.rs - service-common/src/lib.rs
if the Keycloak user is "locked", then also the token should be locked out, right? Currently that doesn't happen.
While there was a decision to only act on changes, it might be ok in cases where the number of applications is low, to still do a periodic reconciliation.
This adds some internal infrastructure for adding more MQTT endpoint dialects. Also doing some example work with: * Web of Things * Cumulocity * Azure IoT
Currently we show the event stream in the "debug" tab on the console. Additionally, we peek at the application logs ourselves when stuff goes wrong (behaves unexpectedly). We should enable...
Long lived connections load the application and device information once, but then keep the originally loaded state until the connection is terminated. One exception is the MQTT endpoint, which already...