Azure/iotedgedev
View on GitHubThe Azure IoT Edge Dev Tool greatly simplifies your Azure IoT Edge development process. It has everything you need to get started and helps with your day-to-day Edge development.
- Stars
- 166
- Forks
- 76
- Open beginner issues
- 0
- Indexed issues
- 42
- Dominant language
- Python
- License
- No license data
- Last GitHub push
- Aug 8, 2026
- Latest indexed
- Sep 14, 2026
- Contributing guide
- Contributing guide
- Code of conduct
- Code of conduct
- Beginner labels
- No beginner labels indexed
- PR merge metrics
- No merged PRs in 30d
-
feature
Azure/iotedgedev#76 · 7 comments · 0 reactions · 0 assignees ·
-
bug
Azure/iotedgedev#218 · 6 comments · 0 reactions · 0 assignees ·
-
Code Signing Openfeature
Azure/iotedgedev#439 · 3 comments · 0 reactions · 0 assignees ·
-
InBacklog
Azure/iotedgedev#455 · 2 comments · 0 reactions · 0 assignees ·
-
InBacklog
Azure/iotedgedev#459 · 4 comments · 0 reactions · 0 assignees ·
-
feature InBacklog one week hack priority:low
Azure/iotedgedev#470 · 0 comments · 0 reactions · 0 assignees ·
-
InBacklog
Azure/iotedgedev#472 · 1 comment · 0 reactions · 0 assignees ·
-
Add support for DPS Openfeature InBacklog one week hack priority:high
Azure/iotedgedev#487 · 2 comments · 0 reactions · 3 assignees ·
-
Azure/iotedgedev#530 · 2 comments · 0 reactions · 0 assignees ·
-
feature one week hack priority:high
Azure/iotedgedev#553 · 0 comments · 0 reactions · 0 assignees ·
-
bug one week hack priority:high
Azure/iotedgedev#561 · 0 comments · 0 reactions · 0 assignees ·
-
bug one week hack priority:low
Azure/iotedgedev#562 · 0 comments · 0 reactions · 0 assignees ·
-
bug one week hack priority:low
Azure/iotedgedev#563 · 0 comments · 0 reactions · 0 assignees ·
-
bug one week hack priority:low
Azure/iotedgedev#564 · 0 comments · 0 reactions · 0 assignees ·
-
bug one week hack priority:low
Azure/iotedgedev#567 · 0 comments · 0 reactions · 1 assignee ·
-
bug InBacklog
Azure/iotedgedev#586 · 1 comment · 0 reactions · 0 assignees ·
-
InBacklog
Azure/iotedgedev#595 · 0 comments · 0 reactions · 0 assignees ·
-
bug InBacklog
Azure/iotedgedev#600 · 2 comments · 0 reactions · 0 assignees ·
-
bug InBacklog
Azure/iotedgedev#601 · 1 comment · 0 reactions · 0 assignees ·
-
bug
Azure/iotedgedev#604 · 3 comments · 1 reaction · 0 assignees ·
-
bug triage
Azure/iotedgedev#605 · 2 comments · 0 reactions · 0 assignees ·
-
bug triage
Azure/iotedgedev#607 · 1 comment · 0 reactions · 0 assignees ·
-
InBacklog
Azure/iotedgedev#608 · 0 comments · 0 reactions · 0 assignees ·
-
bug triage
Azure/iotedgedev#609 · 2 comments · 0 reactions · 0 assignees ·
-
bug triage
Azure/iotedgedev#610 · 1 comment · 0 reactions · 0 assignees ·
-
bug triage
Azure/iotedgedev#611 · 9 comments · 0 reactions · 0 assignees ·
-
feature InBacklog triage
Azure/iotedgedev#613 · 1 comment · 1 reaction · 0 assignees ·
-
feature InBacklog triage
Azure/iotedgedev#616 · 0 comments · 0 reactions · 0 assignees ·
-
bug triage
Azure/iotedgedev#618 · 1 comment · 0 reactions · 0 assignees ·
-
feature triage
Azure/iotedgedev#619 · 1 comment · 4 reactions · 0 assignees ·
-
Azure/iotedgedev#620 · 4 comments · 0 reactions · 0 assignees ·
-
bug triage
Azure/iotedgedev#621 · 12 comments · 2 reactions · 0 assignees ·
-
feature triage
Azure/iotedgedev#622 · 2 comments · 1 reaction · 0 assignees ·
-
bug triage
Azure/iotedgedev#623 · 6 comments · 0 reactions · 0 assignees ·
-
feature triage
Azure/iotedgedev#626 · 0 comments · 0 reactions · 0 assignees ·
-
bug triage
Azure/iotedgedev#627 · 3 comments · 0 reactions · 0 assignees ·
-
feature triage
Azure/iotedgedev#628 · 0 comments · 0 reactions · 0 assignees ·
-
bug triage
Azure/iotedgedev#629 · 6 comments · 0 reactions · 0 assignees ·
-
Azure/iotedgedev#631 · 1 comment · 0 reactions · 0 assignees ·
-
Azure/iotedgedev#632 · 1 comment · 0 reactions · 0 assignees ·
-
feature triage
Azure/iotedgedev#633 · 3 comments · 0 reactions · 0 assignees ·
-
Azure/iotedgedev#634 · 0 comments · 0 reactions · 0 assignees ·