[Event Hubs] Use different env name for EH compatible connection string in IotHub#6614
Merged
ramya-rao-a merged 1 commit intoAzure:masterfrom Dec 18, 2019
Merged
Conversation
ramya-rao-a
requested review from
chradek,
danieljurek and
richardpark-msft
as code owners
chradek
approved these changes
Dec 18, 2019
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
The EPH and EH library tests use different connection strings from IotHub. See #6436 for details.
This PR ensures we use a different env var name for EH such that the same arm template can be used to create resources for both EPH and EH while using different connection strings in tests.
Related to #6563 (comment)