Oracle Cloud Infrastructure v3.10.0 published on Wednesday, Nov 5, 2025 by Pulumi
oci.oci.getIotDigitalTwinAdapter
Oracle Cloud Infrastructure v3.10.0 published on Wednesday, Nov 5, 2025 by Pulumi
This data source provides details about a specific Digital Twin Adapter resource in Oracle Cloud Infrastructure Iot service.
Retrieves the digital twin adapter identified by the specified OCID.
Example Usage
import * as pulumi from "@pulumi/pulumi";
import * as oci from "@pulumi/oci";
const testDigitalTwinAdapter = oci.oci.getIotDigitalTwinAdapter({
digitalTwinAdapterId: testDigitalTwinAdapterOciIotDigitalTwinAdapter.id,
});
import pulumi
import pulumi_oci as oci
test_digital_twin_adapter = oci.oci.get_iot_digital_twin_adapter(digital_twin_adapter_id=test_digital_twin_adapter_oci_iot_digital_twin_adapter["id"])
package main
import (
"github.com/pulumi/pulumi-oci/sdk/v3/go/oci/oci"
"github.com/pulumi/pulumi/sdk/v3/go/pulumi"
)
func main() {
pulumi.Run(func(ctx *pulumi.Context) error {
_, err := oci.LookupIotDigitalTwinAdapter(ctx, &oci.LookupIotDigitalTwinAdapterArgs{
DigitalTwinAdapterId: testDigitalTwinAdapterOciIotDigitalTwinAdapter.Id,
}, nil)
if err != nil {
return err
}
return nil
})
}
using System.Collections.Generic;
using System.Linq;
using Pulumi;
using Oci = Pulumi.Oci;
return await Deployment.RunAsync(() =>
{
var testDigitalTwinAdapter = Oci.Oci.GetIotDigitalTwinAdapter.Invoke(new()
{
DigitalTwinAdapterId = testDigitalTwinAdapterOciIotDigitalTwinAdapter.Id,
});
});
package generated_program;
import com.pulumi.Context;
import com.pulumi.Pulumi;
import com.pulumi.core.Output;
import com.pulumi.oci.oci.OciFunctions;
import com.pulumi.oci.oci.inputs.GetIotDigitalTwinAdapterArgs;
import java.util.List;
import java.util.ArrayList;
import java.util.Map;
import java.io.File;
import java.nio.file.Files;
import java.nio.file.Paths;
public class App {
public static void main(String[] args) {
Pulumi.run(App::stack);
}
public static void stack(Context ctx) {
final var testDigitalTwinAdapter = OciFunctions.getIotDigitalTwinAdapter(GetIotDigitalTwinAdapterArgs.builder()
.digitalTwinAdapterId(testDigitalTwinAdapterOciIotDigitalTwinAdapter.id())
.build());
}
}
variables:
testDigitalTwinAdapter:
fn::invoke:
function: oci:oci:getIotDigitalTwinAdapter
arguments:
digitalTwinAdapterId: ${testDigitalTwinAdapterOciIotDigitalTwinAdapter.id}
Using getIotDigitalTwinAdapter
Two invocation forms are available. The direct form accepts plain arguments and either blocks until the result value is available, or returns a Promise-wrapped result. The output form accepts Input-wrapped arguments and returns an Output-wrapped result.
function getIotDigitalTwinAdapter(args: GetIotDigitalTwinAdapterArgs, opts?: InvokeOptions): Promise<GetIotDigitalTwinAdapterResult>
function getIotDigitalTwinAdapterOutput(args: GetIotDigitalTwinAdapterOutputArgs, opts?: InvokeOptions): Output<GetIotDigitalTwinAdapterResult>def get_iot_digital_twin_adapter(digital_twin_adapter_id: Optional[str] = None,
opts: Optional[InvokeOptions] = None) -> GetIotDigitalTwinAdapterResult
def get_iot_digital_twin_adapter_output(digital_twin_adapter_id: Optional[pulumi.Input[str]] = None,
opts: Optional[InvokeOptions] = None) -> Output[GetIotDigitalTwinAdapterResult]func LookupIotDigitalTwinAdapter(ctx *Context, args *LookupIotDigitalTwinAdapterArgs, opts ...InvokeOption) (*LookupIotDigitalTwinAdapterResult, error)
func LookupIotDigitalTwinAdapterOutput(ctx *Context, args *LookupIotDigitalTwinAdapterOutputArgs, opts ...InvokeOption) LookupIotDigitalTwinAdapterResultOutput> Note: This function is named LookupIotDigitalTwinAdapter in the Go SDK.
public static class GetIotDigitalTwinAdapter
{
public static Task<GetIotDigitalTwinAdapterResult> InvokeAsync(GetIotDigitalTwinAdapterArgs args, InvokeOptions? opts = null)
public static Output<GetIotDigitalTwinAdapterResult> Invoke(GetIotDigitalTwinAdapterInvokeArgs args, InvokeOptions? opts = null)
}public static CompletableFuture<GetIotDigitalTwinAdapterResult> getIotDigitalTwinAdapter(GetIotDigitalTwinAdapterArgs args, InvokeOptions options)
public static Output<GetIotDigitalTwinAdapterResult> getIotDigitalTwinAdapter(GetIotDigitalTwinAdapterArgs args, InvokeOptions options)
fn::invoke:
function: oci:oci/getIotDigitalTwinAdapter:getIotDigitalTwinAdapter
arguments:
# arguments dictionaryThe following arguments are supported:
- Digital
Twin stringAdapter Id - The OCID of the digital twin adapter.
- Digital
Twin stringAdapter Id - The OCID of the digital twin adapter.
- digital
Twin StringAdapter Id - The OCID of the digital twin adapter.
- digital
Twin stringAdapter Id - The OCID of the digital twin adapter.
- digital_
twin_ stradapter_ id - The OCID of the digital twin adapter.
- digital
Twin StringAdapter Id - The OCID of the digital twin adapter.
getIotDigitalTwinAdapter Result
The following output properties are available:
- Dictionary<string, string>
- Defined tags for this resource. Each key is predefined and scoped to a namespace. For more information, see Resource Tags. Example:
{"Operations.CostCenter": "42"} - Description string
- Meaningful write up about the inbound route.
- Digital
Twin stringAdapter Id - Digital
Twin stringModel Id - The OCID of the digital twin model.
- Digital
Twin stringModel Spec Uri - The URI of the digital twin model specification.
- Display
Name string - A user-friendly name. Does not have to be unique, and it's changeable. Avoid entering confidential information.
- Dictionary<string, string>
- Free-form tags for this resource. Each tag is a simple key-value pair with no predefined name, type, or namespace. For more information, see Resource Tags. Example:
{"Department": "Finance"} - Id string
- The OCID of the resource.
- Inbound
Envelopes List<GetIot Digital Twin Adapter Inbound Envelope> - Payload containing device-specific metadata and optional value mappings used to interpret or transform that metadata. This structure includes the device endpoint, the actual payload, and an optional envelope mapping that applies JQ expressions to extract or reshape the data as needed.
- Inbound
Routes List<GetIot Digital Twin Adapter Inbound Route> - list of routes
- Iot
Domain stringId - The OCID of the IoT domain.
- State string
- The current state of the digital twin adapter.
- Dictionary<string, string>
- System tags for this resource. Each key is predefined and scoped to a namespace. Example:
{"orcl-cloud.free-tier-retained": "true"} - Time
Created string - The date and time when the resource was created, in the format defined by RFC 3339. Example:
2016-08-25T21:10:29.600Z - Time
Updated string - The date and time when the resource was last updated, in the format defined by RFC 3339. Example:
2016-08-25T21:10:29.600Z
- map[string]string
- Defined tags for this resource. Each key is predefined and scoped to a namespace. For more information, see Resource Tags. Example:
{"Operations.CostCenter": "42"} - Description string
- Meaningful write up about the inbound route.
- Digital
Twin stringAdapter Id - Digital
Twin stringModel Id - The OCID of the digital twin model.
- Digital
Twin stringModel Spec Uri - The URI of the digital twin model specification.
- Display
Name string - A user-friendly name. Does not have to be unique, and it's changeable. Avoid entering confidential information.
- map[string]string
- Free-form tags for this resource. Each tag is a simple key-value pair with no predefined name, type, or namespace. For more information, see Resource Tags. Example:
{"Department": "Finance"} - Id string
- The OCID of the resource.
- Inbound
Envelopes []GetIot Digital Twin Adapter Inbound Envelope - Payload containing device-specific metadata and optional value mappings used to interpret or transform that metadata. This structure includes the device endpoint, the actual payload, and an optional envelope mapping that applies JQ expressions to extract or reshape the data as needed.
- Inbound
Routes []GetIot Digital Twin Adapter Inbound Route - list of routes
- Iot
Domain stringId - The OCID of the IoT domain.
- State string
- The current state of the digital twin adapter.
- map[string]string
- System tags for this resource. Each key is predefined and scoped to a namespace. Example:
{"orcl-cloud.free-tier-retained": "true"} - Time
Created string - The date and time when the resource was created, in the format defined by RFC 3339. Example:
2016-08-25T21:10:29.600Z - Time
Updated string - The date and time when the resource was last updated, in the format defined by RFC 3339. Example:
2016-08-25T21:10:29.600Z
- Map<String,String>
- Defined tags for this resource. Each key is predefined and scoped to a namespace. For more information, see Resource Tags. Example:
{"Operations.CostCenter": "42"} - description String
- Meaningful write up about the inbound route.
- digital
Twin StringAdapter Id - digital
Twin StringModel Id - The OCID of the digital twin model.
- digital
Twin StringModel Spec Uri - The URI of the digital twin model specification.
- display
Name String - A user-friendly name. Does not have to be unique, and it's changeable. Avoid entering confidential information.
- Map<String,String>
- Free-form tags for this resource. Each tag is a simple key-value pair with no predefined name, type, or namespace. For more information, see Resource Tags. Example:
{"Department": "Finance"} - id String
- The OCID of the resource.
- inbound
Envelopes List<GetIot Digital Twin Adapter Inbound Envelope> - Payload containing device-specific metadata and optional value mappings used to interpret or transform that metadata. This structure includes the device endpoint, the actual payload, and an optional envelope mapping that applies JQ expressions to extract or reshape the data as needed.
- inbound
Routes List<GetIot Digital Twin Adapter Inbound Route> - list of routes
- iot
Domain StringId - The OCID of the IoT domain.
- state String
- The current state of the digital twin adapter.
- Map<String,String>
- System tags for this resource. Each key is predefined and scoped to a namespace. Example:
{"orcl-cloud.free-tier-retained": "true"} - time
Created String - The date and time when the resource was created, in the format defined by RFC 3339. Example:
2016-08-25T21:10:29.600Z - time
Updated String - The date and time when the resource was last updated, in the format defined by RFC 3339. Example:
2016-08-25T21:10:29.600Z
- {[key: string]: string}
- Defined tags for this resource. Each key is predefined and scoped to a namespace. For more information, see Resource Tags. Example:
{"Operations.CostCenter": "42"} - description string
- Meaningful write up about the inbound route.
- digital
Twin stringAdapter Id - digital
Twin stringModel Id - The OCID of the digital twin model.
- digital
Twin stringModel Spec Uri - The URI of the digital twin model specification.
- display
Name string - A user-friendly name. Does not have to be unique, and it's changeable. Avoid entering confidential information.
- {[key: string]: string}
- Free-form tags for this resource. Each tag is a simple key-value pair with no predefined name, type, or namespace. For more information, see Resource Tags. Example:
{"Department": "Finance"} - id string
- The OCID of the resource.
- inbound
Envelopes GetIot Digital Twin Adapter Inbound Envelope[] - Payload containing device-specific metadata and optional value mappings used to interpret or transform that metadata. This structure includes the device endpoint, the actual payload, and an optional envelope mapping that applies JQ expressions to extract or reshape the data as needed.
- inbound
Routes GetIot Digital Twin Adapter Inbound Route[] - list of routes
- iot
Domain stringId - The OCID of the IoT domain.
- state string
- The current state of the digital twin adapter.
- {[key: string]: string}
- System tags for this resource. Each key is predefined and scoped to a namespace. Example:
{"orcl-cloud.free-tier-retained": "true"} - time
Created string - The date and time when the resource was created, in the format defined by RFC 3339. Example:
2016-08-25T21:10:29.600Z - time
Updated string - The date and time when the resource was last updated, in the format defined by RFC 3339. Example:
2016-08-25T21:10:29.600Z
- Mapping[str, str]
- Defined tags for this resource. Each key is predefined and scoped to a namespace. For more information, see Resource Tags. Example:
{"Operations.CostCenter": "42"} - description str
- Meaningful write up about the inbound route.
- digital_
twin_ stradapter_ id - digital_
twin_ strmodel_ id - The OCID of the digital twin model.
- digital_
twin_ strmodel_ spec_ uri - The URI of the digital twin model specification.
- display_
name str - A user-friendly name. Does not have to be unique, and it's changeable. Avoid entering confidential information.
- Mapping[str, str]
- Free-form tags for this resource. Each tag is a simple key-value pair with no predefined name, type, or namespace. For more information, see Resource Tags. Example:
{"Department": "Finance"} - id str
- The OCID of the resource.
- inbound_
envelopes Sequence[GetIot Digital Twin Adapter Inbound Envelope] - Payload containing device-specific metadata and optional value mappings used to interpret or transform that metadata. This structure includes the device endpoint, the actual payload, and an optional envelope mapping that applies JQ expressions to extract or reshape the data as needed.
- inbound_
routes Sequence[GetIot Digital Twin Adapter Inbound Route] - list of routes
- iot_
domain_ strid - The OCID of the IoT domain.
- state str
- The current state of the digital twin adapter.
- Mapping[str, str]
- System tags for this resource. Each key is predefined and scoped to a namespace. Example:
{"orcl-cloud.free-tier-retained": "true"} - time_
created str - The date and time when the resource was created, in the format defined by RFC 3339. Example:
2016-08-25T21:10:29.600Z - time_
updated str - The date and time when the resource was last updated, in the format defined by RFC 3339. Example:
2016-08-25T21:10:29.600Z
- Map<String>
- Defined tags for this resource. Each key is predefined and scoped to a namespace. For more information, see Resource Tags. Example:
{"Operations.CostCenter": "42"} - description String
- Meaningful write up about the inbound route.
- digital
Twin StringAdapter Id - digital
Twin StringModel Id - The OCID of the digital twin model.
- digital
Twin StringModel Spec Uri - The URI of the digital twin model specification.
- display
Name String - A user-friendly name. Does not have to be unique, and it's changeable. Avoid entering confidential information.
- Map<String>
- Free-form tags for this resource. Each tag is a simple key-value pair with no predefined name, type, or namespace. For more information, see Resource Tags. Example:
{"Department": "Finance"} - id String
- The OCID of the resource.
- inbound
Envelopes List<Property Map> - Payload containing device-specific metadata and optional value mappings used to interpret or transform that metadata. This structure includes the device endpoint, the actual payload, and an optional envelope mapping that applies JQ expressions to extract or reshape the data as needed.
- inbound
Routes List<Property Map> - list of routes
- iot
Domain StringId - The OCID of the IoT domain.
- state String
- The current state of the digital twin adapter.
- Map<String>
- System tags for this resource. Each key is predefined and scoped to a namespace. Example:
{"orcl-cloud.free-tier-retained": "true"} - time
Created String - The date and time when the resource was created, in the format defined by RFC 3339. Example:
2016-08-25T21:10:29.600Z - time
Updated String - The date and time when the resource was last updated, in the format defined by RFC 3339. Example:
2016-08-25T21:10:29.600Z
Supporting Types
GetIotDigitalTwinAdapterInboundEnvelope
- Envelope
Mappings List<GetIot Digital Twin Adapter Inbound Envelope Envelope Mapping> - Maps the metadata fields from the inbound payload using JQ. These mappings allow you to extract specific metadata such as timestamps using JQ expressions.
- Reference
Endpoint string - The device endpoint.
- Reference
Payloads List<GetIot Digital Twin Adapter Inbound Envelope Reference Payload> - Reference payload structure template received from IoT device. This payload must specify its content type using the
dataFormatproperty.
- Envelope
Mappings []GetIot Digital Twin Adapter Inbound Envelope Envelope Mapping - Maps the metadata fields from the inbound payload using JQ. These mappings allow you to extract specific metadata such as timestamps using JQ expressions.
- Reference
Endpoint string - The device endpoint.
- Reference
Payloads []GetIot Digital Twin Adapter Inbound Envelope Reference Payload - Reference payload structure template received from IoT device. This payload must specify its content type using the
dataFormatproperty.
- envelope
Mappings List<GetIot Digital Twin Adapter Inbound Envelope Envelope Mapping> - Maps the metadata fields from the inbound payload using JQ. These mappings allow you to extract specific metadata such as timestamps using JQ expressions.
- reference
Endpoint String - The device endpoint.
- reference
Payloads List<GetIot Digital Twin Adapter Inbound Envelope Reference Payload> - Reference payload structure template received from IoT device. This payload must specify its content type using the
dataFormatproperty.
- envelope
Mappings GetIot Digital Twin Adapter Inbound Envelope Envelope Mapping[] - Maps the metadata fields from the inbound payload using JQ. These mappings allow you to extract specific metadata such as timestamps using JQ expressions.
- reference
Endpoint string - The device endpoint.
- reference
Payloads GetIot Digital Twin Adapter Inbound Envelope Reference Payload[] - Reference payload structure template received from IoT device. This payload must specify its content type using the
dataFormatproperty.
- envelope_
mappings Sequence[GetIot Digital Twin Adapter Inbound Envelope Envelope Mapping] - Maps the metadata fields from the inbound payload using JQ. These mappings allow you to extract specific metadata such as timestamps using JQ expressions.
- reference_
endpoint str - The device endpoint.
- reference_
payloads Sequence[GetIot Digital Twin Adapter Inbound Envelope Reference Payload] - Reference payload structure template received from IoT device. This payload must specify its content type using the
dataFormatproperty.
- envelope
Mappings List<Property Map> - Maps the metadata fields from the inbound payload using JQ. These mappings allow you to extract specific metadata such as timestamps using JQ expressions.
- reference
Endpoint String - The device endpoint.
- reference
Payloads List<Property Map> - Reference payload structure template received from IoT device. This payload must specify its content type using the
dataFormatproperty.
GetIotDigitalTwinAdapterInboundEnvelopeEnvelopeMapping
- Time
Observed string - JQ expression to extract the observation timestamp from the payload. If not specified, the system will default to using
timeReceivedas the timestamp. Example: For payload{"time": "<timestamp>","temp": 65,"hum": 55}'timeObserved' can be mapped as JQ Expression$.time.
- Time
Observed string - JQ expression to extract the observation timestamp from the payload. If not specified, the system will default to using
timeReceivedas the timestamp. Example: For payload{"time": "<timestamp>","temp": 65,"hum": 55}'timeObserved' can be mapped as JQ Expression$.time.
- time
Observed String - JQ expression to extract the observation timestamp from the payload. If not specified, the system will default to using
timeReceivedas the timestamp. Example: For payload{"time": "<timestamp>","temp": 65,"hum": 55}'timeObserved' can be mapped as JQ Expression$.time.
- time
Observed string - JQ expression to extract the observation timestamp from the payload. If not specified, the system will default to using
timeReceivedas the timestamp. Example: For payload{"time": "<timestamp>","temp": 65,"hum": 55}'timeObserved' can be mapped as JQ Expression$.time.
- time_
observed str - JQ expression to extract the observation timestamp from the payload. If not specified, the system will default to using
timeReceivedas the timestamp. Example: For payload{"time": "<timestamp>","temp": 65,"hum": 55}'timeObserved' can be mapped as JQ Expression$.time.
- time
Observed String - JQ expression to extract the observation timestamp from the payload. If not specified, the system will default to using
timeReceivedas the timestamp. Example: For payload{"time": "<timestamp>","temp": 65,"hum": 55}'timeObserved' can be mapped as JQ Expression$.time.
GetIotDigitalTwinAdapterInboundEnvelopeReferencePayload
- Data Dictionary<string, string>
- JSON raw data.
- Data
Format string - Data format of the payload.
- Data map[string]string
- JSON raw data.
- Data
Format string - Data format of the payload.
- data Map<String,String>
- JSON raw data.
- data
Format String - Data format of the payload.
- data {[key: string]: string}
- JSON raw data.
- data
Format string - Data format of the payload.
- data Mapping[str, str]
- JSON raw data.
- data_
format str - Data format of the payload.
- data Map<String>
- JSON raw data.
- data
Format String - Data format of the payload.
GetIotDigitalTwinAdapterInboundRoute
- Condition string
- A boolean expression used to determine whether the following transformation should be processed for the incoming payload. This expression is typically based on fields defined at the inbound Envelope and is evaluated before applying the
payloadMapping. - Description string
- Meaningful write up about the inbound route.
- Payload
Mapping Dictionary<string, string> - A set of key-value JQ expressions used to transform the incoming payload into a shape compatible with the digital twin model's context or schema.
- Reference
Payloads List<GetIot Digital Twin Adapter Inbound Route Reference Payload> - Reference payload structure template received from IoT device. This payload must specify its content type using the
dataFormatproperty.
- Condition string
- A boolean expression used to determine whether the following transformation should be processed for the incoming payload. This expression is typically based on fields defined at the inbound Envelope and is evaluated before applying the
payloadMapping. - Description string
- Meaningful write up about the inbound route.
- Payload
Mapping map[string]string - A set of key-value JQ expressions used to transform the incoming payload into a shape compatible with the digital twin model's context or schema.
- Reference
Payloads []GetIot Digital Twin Adapter Inbound Route Reference Payload - Reference payload structure template received from IoT device. This payload must specify its content type using the
dataFormatproperty.
- condition String
- A boolean expression used to determine whether the following transformation should be processed for the incoming payload. This expression is typically based on fields defined at the inbound Envelope and is evaluated before applying the
payloadMapping. - description String
- Meaningful write up about the inbound route.
- payload
Mapping Map<String,String> - A set of key-value JQ expressions used to transform the incoming payload into a shape compatible with the digital twin model's context or schema.
- reference
Payloads List<GetIot Digital Twin Adapter Inbound Route Reference Payload> - Reference payload structure template received from IoT device. This payload must specify its content type using the
dataFormatproperty.
- condition string
- A boolean expression used to determine whether the following transformation should be processed for the incoming payload. This expression is typically based on fields defined at the inbound Envelope and is evaluated before applying the
payloadMapping. - description string
- Meaningful write up about the inbound route.
- payload
Mapping {[key: string]: string} - A set of key-value JQ expressions used to transform the incoming payload into a shape compatible with the digital twin model's context or schema.
- reference
Payloads GetIot Digital Twin Adapter Inbound Route Reference Payload[] - Reference payload structure template received from IoT device. This payload must specify its content type using the
dataFormatproperty.
- condition str
- A boolean expression used to determine whether the following transformation should be processed for the incoming payload. This expression is typically based on fields defined at the inbound Envelope and is evaluated before applying the
payloadMapping. - description str
- Meaningful write up about the inbound route.
- payload_
mapping Mapping[str, str] - A set of key-value JQ expressions used to transform the incoming payload into a shape compatible with the digital twin model's context or schema.
- reference_
payloads Sequence[GetIot Digital Twin Adapter Inbound Route Reference Payload] - Reference payload structure template received from IoT device. This payload must specify its content type using the
dataFormatproperty.
- condition String
- A boolean expression used to determine whether the following transformation should be processed for the incoming payload. This expression is typically based on fields defined at the inbound Envelope and is evaluated before applying the
payloadMapping. - description String
- Meaningful write up about the inbound route.
- payload
Mapping Map<String> - A set of key-value JQ expressions used to transform the incoming payload into a shape compatible with the digital twin model's context or schema.
- reference
Payloads List<Property Map> - Reference payload structure template received from IoT device. This payload must specify its content type using the
dataFormatproperty.
GetIotDigitalTwinAdapterInboundRouteReferencePayload
- Data Dictionary<string, string>
- JSON raw data.
- Data
Format string - Data format of the payload.
- Data map[string]string
- JSON raw data.
- Data
Format string - Data format of the payload.
- data Map<String,String>
- JSON raw data.
- data
Format String - Data format of the payload.
- data {[key: string]: string}
- JSON raw data.
- data
Format string - Data format of the payload.
- data Mapping[str, str]
- JSON raw data.
- data_
format str - Data format of the payload.
- data Map<String>
- JSON raw data.
- data
Format String - Data format of the payload.
Package Details
- Repository
- oci pulumi/pulumi-oci
- License
- Apache-2.0
- Notes
- This Pulumi package is based on the
ociTerraform Provider.
Oracle Cloud Infrastructure v3.10.0 published on Wednesday, Nov 5, 2025 by Pulumi
