You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
refactor: enforce single thing type per thing (AWS IoT limitation)
AWS IoT Core allows only one thing type per thing. Refactored codebase
to remove plural thing type support and enforce singular thing type.
Changes:
- Removed IoTThingTypes parameter and THING_TYPE_NAMES env var
- Updated product_verifier to only handle THING_TYPE_NAME (singular)
- Simplified bulk_importer to process single thing type
- Updated E2E test framework for singular thing type validation
- Fixed unit test isolation issues (env var cleanup in tearDown)
- Updated all documentation (MULTI_ATTACHMENT_GUIDE.md and vendor docs)
Breaking change: IoTThingTypes parameter removed. Use IoTThingType instead.
All unit tests passing (160 passed, 1 xpassed)
Copy file name to clipboardExpand all lines: docs/MULTI_ATTACHMENT_GUIDE.md
+18-11Lines changed: 18 additions & 11 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -2,7 +2,7 @@
2
2
3
3
## Overview
4
4
5
-
Thingpress now supports attaching multiple policies, thing groups, and thing types to each certificate/thing. This enables enterprise IoT deployment patterns with hierarchical organization.
5
+
Thingpress supports attaching multiple policiesand thing groups to each certificate/thing. **Note: AWS IoT Core allows only one thing type per thing.**
6
6
7
7
## Parameter Syntax
8
8
@@ -14,7 +14,7 @@ Use comma-delimited lists for multiple values:
0 commit comments