Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Publish descriptive MQTT message on upload to Blob Storage #525

Open
tsundvoll opened this issue Feb 28, 2024 · 1 comment
Open

Publish descriptive MQTT message on upload to Blob Storage #525

tsundvoll opened this issue Feb 28, 2024 · 1 comment
Assignees
Labels
feature New feature or request stale This issue or pull request already exists

Comments

@tsundvoll
Copy link
Contributor

Describe the new feature you would like to see
When an inspection result is stored in Blob Storage, a reference to the data should be provided in a message on the "inspection_result" topic over MQTT. It should be possible for another system to later retrieve the inspection result from the blob storage using only the information provided in the message.

Describe the solution you'd like
When an image or another inspection result is stored in a blob storage, retrieve information about how this can be accessed later. Part of the issue is to figure out technically how this is done with blob storage, whether it is an ID or an url etc.

Make sure this ID / URL / other reference is published over MQTT on the "inspection_result" topic. Something similar is already in place, but I suspect the ID provided is not working.

A good starting point is the isar/storage/uploader.py and isar/storage/blob_storage modules, where a message is published to the "inspection_result" topic.

Verify that such a message can be received and that the information provided is enough to retrieve the inspection result back from the blob storage.

How will this feature affect the current Threat Model?
N/A

@aeshub
Copy link
Contributor

aeshub commented May 8, 2024

This issue has automatically been marked as stale as there has been no activity for 60 days.

@aeshub aeshub added the stale This issue or pull request already exists label May 8, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
feature New feature or request stale This issue or pull request already exists
Projects
None yet
4 participants