iothub
: Support Identity-Based Endpoint
#14705
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Cont. of #14354. Adding support for identity-based authentication to custom routing endpoint of iot hub. There are four endpoint resources and the main iot_hub resource. Fix #9139
eventhub
,servicebus_queue
andservicebus_topic
authentication_type
: whether to usekeyBased
(default) oridentityBased
identity_id
: user-assigned managed identity id when usingidentityBased
endpoint_uri
andentity_path
: set together, to specify the target endpoint inidentityBased
caseconnection_string
: update fromRequired
toOptional
, this is used inkeyBased
casestorage_container
authentication_type
,identity_id
,endpoint_uri
,connection_string
: same as above.entity_path
is not applicable becausecontainer_name
is already usediothub
Endpoints can be specified directly on iothub, above properties are added here as well. Due to the limitation of schema in a TypeList, restrictions of these properties are put into code instead.
Test result: