axiscommunications / acap-integration-examples-azure

Integration between Axis devices and Microsoft Azure

Copyright (C) 2022, Axis Communications AB, Lund, Sweden. All Rights Reserved.

Integration between Axis devices and Azure

Introduction

AXIS Camera Application Platform (ACAP) is an open platform that enables developer to build applications that can be installed on Axis network cameras and video encoders.

Azure is a platform in the cloud that provides highly reliable, scalable, low-cost infrastructure to individuals, companies, and governments.

This repository focuses on providing examples where we create the integration between the Axis device and Azure. If you are interested in camera applications and the different API surfaces an application can use, please visit our related repository AxisCommunications/acap3-examples.

Example applications

The repository contains a set of examples, each tailored towards a specific problem. All examples have a README file in its directory which shows overview, example directory structure and step-by-step instructions on how to deploy the Azure infrastructure and how to configure the camera to interact with Azure.

If you find yourself wishing there was another example more relevant to your use case, please don't hesitate to start a discussion or open a new issue.

• images-to-azure-storage-account
  • This example covers sending images from a camera to a storage account in Azure
• telemetry-to-azure-iot-edge
  • This example covers sending telemetry from a camera to IoT Edge on-premises
• telemetry-to-azure-iot-hub
  • This example covers sending telemetry from a camera to an IoT Hub in Azure

License

Apache 2.0

acap-integration-examples-azure's Issues

Dependency Dashboard

This issue lists Renovate updates and detected dependencies. Read the Dependency Dashboard docs to learn more.

Edited/Blocked

These updates have been manually edited so Renovate will no longer make changes. To discard all commits and start over, click on a checkbox.

• chore(deps): update resource microsoft.apimanagement/service to 2022-08-01
• chore(deps): update resource microsoft.authorization/roleassignments to 2022-04-01
• chore(deps): update resource microsoft.devices/iothubs to 2023-06-30
• chore(deps): update resource microsoft.keyvault/vaults to 2023-07-01
• chore(deps): update resource microsoft.managedidentity/userassignedidentities to 2023-01-31
• chore(deps): update resource microsoft.resources/deploymentscripts to 2023-08-01
• chore(deps): update resource microsoft.storage/storageaccounts to 2023-04-01

Open

These updates have all been created already. Click a checkbox below to force a retry/rebase of any.

• chore(deps): update actions/checkout action to v4
• chore(deps): update github/super-linter action to v6

Detected dependencies

bicep

images-to-azure-storage-account/main.bicep

• Microsoft.Storage/storageAccounts 2021-04-01
• Microsoft.Authorization/roleAssignments 2020-08-01-preview
• Microsoft.ApiManagement/service 2021-01-01-preview

telemetry-to-azure-iot-hub/main.bicep

• Microsoft.Devices/IotHubs 2021-03-31
• Microsoft.ManagedIdentity/userAssignedIdentities 2018-11-30
• Microsoft.Authorization/roleAssignments 2020-08-01-preview
• Microsoft.KeyVault/vaults 2021-06-01-preview
• Microsoft.Resources/deploymentScripts 2020-10-01

github-actions

.github/workflows/bicep-to-arm.yml

• actions/checkout v3

.github/workflows/images-to-azure-storage-account.yml

• actions/checkout v3

.github/workflows/lint.yml

• actions/checkout v3
• github/super-linter v5

.github/workflows/static-uri.yml

.github/workflows/telemetry-to-azure-iot-edge.yml

• actions/checkout v3

.github/workflows/telemetry-to-azure-iot-hub.yml

• actions/checkout v3

---

• Check this box to trigger a request for Renovate to run again on this repository

Bug in Azure CLI v2.30.0 on macOS prohibits running deployment script

A possible bug in Azure CLI, v2.30.0, on macOS has been found and reported to Azure/azure-cli#20336. This bug is mentioned in the README of the example.

Let's monitor the issue and see whether it is a bug or just an issue on our side.

Enable DPS for device connection to IoT Hub

Describe the feature

The current solution to connect an axis camera to IoT Hub means if there is an issue with the specific IoT Hub we will have some down time. Most devices nowadays connect to Azure using DPS (Device Provisioning Service) system. This allows us to use IoT Central which connects to an IoT Hub but can switch to another hub if it goes down without any disruption to the data.

Added value

Nowadays, most devices have options to connect via DPS to help mitigate any system downtime due to IoT Hub failures. Please let me know if this is a way we can connect the axis cameras to IoT Hub.

Markdownlint

It seems there is no markdownlint in the GitHub CI workflows, but the markdown files in the repo contain issues that should need to be mitigated.