Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Added support for EventHub compatible EndPoints and Paths #1789

Conversation

szaroubi
Copy link
Contributor

@szaroubi szaroubi commented Aug 17, 2018

Hello I am looking for feedback on this pull request.
The PR is the fulfill this feature request: #1743

It's a simple pull request whose objective is to expose the Endpoint and Path properties of each Endpoint in the Events Hub Compatible endpoints that the IoT Gateway exposes.

I created 4 new properties:

event_hub_events_endpoint
event_hub_events_path
event_hub_operations_endpoint
event_hub_operations_path

Fixes #1743

@szaroubi
Copy link
Contributor Author

Just updated documentation to reflect the 4 new exposed properties.

@szaroubi szaroubi changed the title [WIP] issues:1743 | Added support for EventHub compatible EndPoints and Paths [WIP] issues: #1743 | Added support for EventHub compatible EndPoints and Paths Aug 17, 2018
@szaroubi szaroubi changed the title [WIP] issues: #1743 | Added support for EventHub compatible EndPoints and Paths Added support for EventHub compatible EndPoints and Paths Aug 17, 2018
Copy link
Contributor

@tombuildsstuff tombuildsstuff left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

hey @szaroubi

Thanks for this PR - I've taken a look through and have left one comment (which I'm going to push a commit to fix) - but this otherwise LGTM 👍

Thanks!

@@ -68,6 +68,10 @@ The following attributes are exported:

* `shared_access_policy` - One or more `shared_access_policy` blocks as defined below.

* `event_hub_[events|operations]_endpoint` - The EventHub compatible endpoint for either the events or operational data (in conjunction with the path and share access policy, can be used to build a connection string)

* `event_hub_[events|operations]_path` - The EventHub compatible path for either the events or operational data (in conjunction with the endpoint and share access policy, can be used to build a connection string).
Copy link
Contributor

@tombuildsstuff tombuildsstuff Aug 21, 2018

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

can we make this:

* `event_hub_events_endpoint` -  The EventHub compatible endpoint for events data
* `event_hub_events_path` -  The EventHub compatible path for events data
* `event_hub_operations_endpoint` -  The EventHub compatible endpoint for operational data
* `event_hub_operations_path` -  The EventHub compatible path for operational data

-> **NOTE:** These fields can be used in conjunction with the `shared_access_policy` block to build a connection string

@tombuildsstuff
Copy link
Contributor

Tests pass:

screenshot 2018-08-21 at 10 08 12

@tombuildsstuff tombuildsstuff merged commit b75a79f into hashicorp:master Aug 21, 2018
@tombuildsstuff tombuildsstuff added this to the 1.14.0 milestone Aug 21, 2018
tombuildsstuff added a commit that referenced this pull request Aug 21, 2018
torresdal added a commit to torresdal/terraform-provider-azurerm that referenced this pull request Aug 23, 2018
* master: (95 commits)
  Some more AzureStack changes for route table resource and datasource (hashicorp#1807)
  backport AzureStack route resource PR comments (hashicorp#1810)
  Updating to include hashicorp#1799
  Bug Fix of azurerm_virtual_machine.storage_os_disk.image_uri (hashicorp#1799)
  Updating to include hashicorp#1693
  IoT Hub add endpoints and routes (hashicorp#1693)
  Updating to include hashicorp#1789
  Added support for EventHub compatible EndPoints and Paths (hashicorp#1789)
  Updating to include hashicorp#1798
  Remove client side validation for azure network plugin (hashicorp#1798)
  backport azure stack route_table PR review comments (hashicorp#1790)
  Update CHAGELOG.md to include hashicorp#1795
  Fix: Corrected regexp for eventhub name
  reset verb
  fix some pointer dereferences
  Fix indentation on application_gateway.html.markdown (hashicorp#1780)
  folded subscription and [az]schema packages into azure
  consolidate CaseDifference Supression functions
  Cleanup after v1.13.0 release
  v1.13.0
  ...
@ghost
Copy link

ghost commented Mar 30, 2020

I'm going to lock this issue because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues.

If you feel this issue should be reopened, we encourage creating a new issue linking back to this one for added context. If you feel I made an error 🤖 🙉 , please reach out to my human friends 👉 hashibot-feedback@hashicorp.com. Thanks!

@ghost ghost locked and limited conversation to collaborators Mar 30, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

IoTHub Connection Strings
2 participants