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

Support for Digital Twins #9211

Closed
yupwei68 opened this issue Nov 9, 2020 · 2 comments · Fixed by #9212, #9489, #9673 or #9702
Closed

Support for Digital Twins #9211

yupwei68 opened this issue Nov 9, 2020 · 2 comments · Fixed by #9212, #9489, #9673 or #9702

Comments

@yupwei68
Copy link
Contributor

yupwei68 commented Nov 9, 2020

Community Note

  • Please vote on this issue by adding a 👍 reaction to the original issue to help the community and maintainers prioritize this request
  • Please do not leave "+1" or "me too" comments, they generate extra noise for issue followers and do not help prioritize the request
  • If you are interested in working on this issue or have submitted a pull request, please leave a comment

Description

Azure Digital Twins is a platform as a service (PaaS) offering that enables the creation of knowledge graphs based on digital models of entire environments.

In an Azure Digital Twins solution, the entities in your environment are represented by Azure digital twins. A digital twin is an instance of one of your custom-defined models. It can be connected to other digital twins via relationships to form a twin graph: this twin graph is the representation of your entire environment.

The data in your Azure Digital Twins model can be routed to downstream Azure services for additional analytics or storage. This is provided through event routes, which use Event Hub, Event Grid, or Service Bus to drive your desired data flows.

There are two major cases for sending Azure Digital Twins data:

  1. Sending data from one twin in the Azure Digital Twins graph to another. For instance, when a property on one digital twin changes, you may want to notify and update another digital twin accordingly.
  2. Sending data to downstream data services for additional storage or processing (also known as data egress). For instance,
    2.1 A hospital may want to send Azure Digital Twins event data to Time Series Insights (TSI), to record time series data of handwashing-related events for bulk analytics.
    2.2 A business that is already using Azure Maps may want to use Azure Digital Twins to enhance their solution. They can quickly enable an Azure Map after setting up Azure Digital Twins, bring Azure Map entities into Azure Digital Twins as digital twins in the twin graph, or run powerful queries leveraging their Azure Maps and Azure Digital Twins data together.

New or Affected Resource(s)

  • azurerm_iothub_digital_twins
  • azurerm_iothub_digital_twins_endpoint_eventhub
  • azurerm_iothub_digital_twins_endpoint_eventgrid
  • azurerm_iothub_digital_twins_endpoint_servicebus

Potential Terraform Configuration

resource "azurerm_iothub_digital_twins" "test" {
  name                = "acctest-DT"
  resource_group_name = azurerm_resource_group.test.name
  location            = azurerm_resource_group.test.location
}

References

@WodansSon WodansSon added this to the v2.38.0 milestone Nov 23, 2020
WodansSon pushed a commit that referenced this issue Nov 23, 2020
* update azure-sdk-for-go to v47.0.0

* update

* update

* update

* update

* update

* fmt

* review

* update

* update

Co-authored-by: arcturusZhang <[email protected]>
@ghost
Copy link

ghost commented Nov 27, 2020

This has been released in version 2.38.0 of the provider. Please see the Terraform documentation on provider versioning or reach out if you need any assistance upgrading. As an example:

provider "azurerm" {
    version = "~> 2.38.0"
}
# ... other configuration ...

WodansSon added a commit that referenced this issue Dec 3, 2020
* update azure-sdk-for-go to v47.0.0

* Updated to v47.1.0

* Update SDK to v48.0.0

* update

* update

* update

* update

* update

* update

* update

* update

* update

* update

* update

* update

* review

* Resolve conflicts

* Rename and move tests

* Fixed test case

* gofmt registration

Co-authored-by: arcturusZhang <[email protected]>
Co-authored-by: Dapeng Zhang <[email protected]>
Co-authored-by: Jeffrey Cline <[email protected]>
WodansSon pushed a commit that referenced this issue Dec 4, 2020
* update azure-sdk-for-go to v47.0.0

* Updated to v47.1.0

* Update SDK to v48.0.0

* update

* update

* update

* update

* update

* update

* update

* update

* update

* update

* update

* update

* review

* rebase

* update

* update

* fmt

* review

* update

Co-authored-by: arcturusZhang <[email protected]>
Co-authored-by: Dapeng Zhang <[email protected]>
@ghost
Copy link

ghost commented Dec 23, 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 👉 [email protected]. Thanks!

@ghost ghost locked as resolved and limited conversation to collaborators Dec 23, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.