pulumi-newrelic 5.20.0a1709365820__py3-none-any.whl → 5.21.0__py3-none-any.whl

pulumi_newrelic/cloud/azure_integrations.py

@@ -1187,6 +1187,7 @@ class AzureIntegrations(pulumi.CustomResource):
 
         Leave an integration block empty to use its default configuration. You can also use the full example, including the Azure set up, found in our guides.
 
+        <!--Start PulumiCodeChooser -->
         ```python
         import pulumi
         import pulumi_newrelic as newrelic
@@ -1336,12 +1337,13 @@ class AzureIntegrations(pulumi.CustomResource):
                 resource_groups=["resource_groups"],
             ))
         ```
+        <!--End PulumiCodeChooser -->
 
         ## Import
 
         Linked Azure accounts can be imported using `id`, you can find the `id` of existing Azure linked accounts in Azure dashboard under Infrastructure in NewRelic.
 
-         bash
+        bash
 
         ```sh
         $ pulumi import newrelic:cloud/azureIntegrations:AzureIntegrations foo <id>
@@ -1409,6 +1411,7 @@ class AzureIntegrations(pulumi.CustomResource):
 
         Leave an integration block empty to use its default configuration. You can also use the full example, including the Azure set up, found in our guides.
 
+        <!--Start PulumiCodeChooser -->
         ```python
         import pulumi
         import pulumi_newrelic as newrelic
@@ -1558,12 +1561,13 @@ class AzureIntegrations(pulumi.CustomResource):
                 resource_groups=["resource_groups"],
             ))
         ```
+        <!--End PulumiCodeChooser -->
 
         ## Import
 
         Linked Azure accounts can be imported using `id`, you can find the `id` of existing Azure linked accounts in Azure dashboard under Infrastructure in NewRelic.
 
-         bash
+        bash
 
         ```sh
         $ pulumi import newrelic:cloud/azureIntegrations:AzureIntegrations foo <id>

pulumi_newrelic/cloud/azure_link_account.py

@@ -242,6 +242,7 @@ class AzureLinkAccount(pulumi.CustomResource):
 
         You can also use the full example, including the Azure set up, found in our guides.
 
+        <!--Start PulumiCodeChooser -->
         ```python
         import pulumi
         import pulumi_newrelic as newrelic
@@ -253,12 +254,13 @@ class AzureLinkAccount(pulumi.CustomResource):
             subscription_id="Subscription ID of Azure",
             tenant_id="Tenant ID of the Azure")
         ```
+        <!--End PulumiCodeChooser -->
 
         ## Import
 
         Linked Azure accounts can be imported using `id`, you can find the `id` of existing Azure linked accounts in Azure dashboard under Infrastructure in NewRelic
 
-         bash
+        bash
 
         ```sh
         $ pulumi import newrelic:cloud/azureLinkAccount:AzureLinkAccount foo <id>
@@ -294,6 +296,7 @@ class AzureLinkAccount(pulumi.CustomResource):
 
         You can also use the full example, including the Azure set up, found in our guides.
 
+        <!--Start PulumiCodeChooser -->
         ```python
         import pulumi
         import pulumi_newrelic as newrelic
@@ -305,12 +308,13 @@ class AzureLinkAccount(pulumi.CustomResource):
             subscription_id="Subscription ID of Azure",
             tenant_id="Tenant ID of the Azure")
         ```
+        <!--End PulumiCodeChooser -->
 
         ## Import
 
         Linked Azure accounts can be imported using `id`, you can find the `id` of existing Azure linked accounts in Azure dashboard under Infrastructure in NewRelic
 
-         bash
+        bash
 
         ```sh
         $ pulumi import newrelic:cloud/azureLinkAccount:AzureLinkAccount foo <id>

pulumi_newrelic/cloud/gcp_integrations.py

@@ -971,6 +971,7 @@ class GcpIntegrations(pulumi.CustomResource):
 
         Leave an integration block empty to use its default configuration. You can also use the full example, including the GCP set up, found in our guides.
 
+        <!--Start PulumiCodeChooser -->
         ```python
         import pulumi
         import pulumi_newrelic as newrelic
@@ -1058,12 +1059,13 @@ class GcpIntegrations(pulumi.CustomResource):
                 metrics_polling_interval=400,
             ))
         ```
+        <!--End PulumiCodeChooser -->
 
         ## Import
 
         Linked GCP account integrations can be imported using the `id`, e.g.
 
-         bash
+        bash
 
         ```sh
         $ pulumi import newrelic:cloud/gcpIntegrations:GcpIntegrations foo <id>
@@ -1119,6 +1121,7 @@ class GcpIntegrations(pulumi.CustomResource):
 
         Leave an integration block empty to use its default configuration. You can also use the full example, including the GCP set up, found in our guides.
 
+        <!--Start PulumiCodeChooser -->
         ```python
         import pulumi
         import pulumi_newrelic as newrelic
@@ -1206,12 +1209,13 @@ class GcpIntegrations(pulumi.CustomResource):
                 metrics_polling_interval=400,
             ))
         ```
+        <!--End PulumiCodeChooser -->
 
         ## Import
 
         Linked GCP account integrations can be imported using the `id`, e.g.
 
-         bash
+        bash
 
         ```sh
         $ pulumi import newrelic:cloud/gcpIntegrations:GcpIntegrations foo <id>

pulumi_newrelic/cloud/gcp_link_account.py

@@ -150,6 +150,7 @@ class GcpLinkAccount(pulumi.CustomResource):
 
         You can also use the full example, including the GCP set up, found in our guides.
 
+        <!--Start PulumiCodeChooser -->
         ```python
         import pulumi
         import pulumi_newrelic as newrelic
@@ -158,12 +159,13 @@ class GcpLinkAccount(pulumi.CustomResource):
             account_id="account id of newrelic account",
             project_id="id of the Project")
         ```
+        <!--End PulumiCodeChooser -->
 
         ## Import
 
         Linked GCP accounts can be imported using `id`, you can find the `id` of an existing GCP linked accounts in GCP dashboard under Infrastructure in Newrelic Console.
 
-         bash
+        bash
 
         ```sh
         $ pulumi import newrelic:cloud/gcpLinkAccount:GcpLinkAccount newrelic_cloud_gcp_link_account.foo <id>
@@ -200,6 +202,7 @@ class GcpLinkAccount(pulumi.CustomResource):
 
         You can also use the full example, including the GCP set up, found in our guides.
 
+        <!--Start PulumiCodeChooser -->
         ```python
         import pulumi
         import pulumi_newrelic as newrelic
@@ -208,12 +211,13 @@ class GcpLinkAccount(pulumi.CustomResource):
             account_id="account id of newrelic account",
             project_id="id of the Project")
         ```
+        <!--End PulumiCodeChooser -->
 
         ## Import
 
         Linked GCP accounts can be imported using `id`, you can find the `id` of an existing GCP linked accounts in GCP dashboard under Infrastructure in Newrelic Console.
 
-         bash
+        bash
 
         ```sh
         $ pulumi import newrelic:cloud/gcpLinkAccount:GcpLinkAccount newrelic_cloud_gcp_link_account.foo <id>

pulumi_newrelic/data_partition_rule.py

@@ -248,6 +248,7 @@ class DataPartitionRule(pulumi.CustomResource):
 
         ## Example Usage
 
+        <!--Start PulumiCodeChooser -->
         ```python
         import pulumi
         import pulumi_newrelic as newrelic
@@ -259,6 +260,8 @@ class DataPartitionRule(pulumi.CustomResource):
             retention_policy="STANDARD",
             target_data_partition="Log_name")
         ```
+        <!--End PulumiCodeChooser -->
+
         ## Additional Information
 
         More details about the data partition can be found [here](https://docs.newrelic.com/docs/logs/ui-data/data-partitions/)
@@ -267,7 +270,7 @@ class DataPartitionRule(pulumi.CustomResource):
 
         New Relic data partition rule can be imported using the rule ID, e.g.
 
-         bash
+        bash
 
         ```sh
         $ pulumi import newrelic:index/dataPartitionRule:DataPartitionRule foo <id>
@@ -293,6 +296,7 @@ class DataPartitionRule(pulumi.CustomResource):
 
         ## Example Usage
 
+        <!--Start PulumiCodeChooser -->
         ```python
         import pulumi
         import pulumi_newrelic as newrelic
@@ -304,6 +308,8 @@ class DataPartitionRule(pulumi.CustomResource):
             retention_policy="STANDARD",
             target_data_partition="Log_name")
         ```
+        <!--End PulumiCodeChooser -->
+
         ## Additional Information
 
         More details about the data partition can be found [here](https://docs.newrelic.com/docs/logs/ui-data/data-partitions/)
@@ -312,7 +318,7 @@ class DataPartitionRule(pulumi.CustomResource):
 
         New Relic data partition rule can be imported using the rule ID, e.g.
 
-         bash
+        bash
 
         ```sh
         $ pulumi import newrelic:index/dataPartitionRule:DataPartitionRule foo <id>

pulumi_newrelic/entity_tags.py

@@ -104,6 +104,7 @@ class EntityTags(pulumi.CustomResource):
 
         ## Example Usage
 
+        <!--Start PulumiCodeChooser -->
         ```python
         import pulumi
         import pulumi_newrelic as newrelic
@@ -127,14 +128,15 @@ class EntityTags(pulumi.CustomResource):
                 ),
             ])
         ```
+        <!--End PulumiCodeChooser -->
 
         ## Import
 
         New Relic One entity tags can be imported using a concatenated string of the format
 
-        `<guid>`, e.g.
+         `<guid>`, e.g.
 
-         bash
+        bash
 
         ```sh
         $ pulumi import newrelic:index/entityTags:EntityTags foo MjUyMDUyOHxBUE18QVBRTElDQVRJT058MjE1MDM3Nzk1
@@ -156,6 +158,7 @@ class EntityTags(pulumi.CustomResource):
 
         ## Example Usage
 
+        <!--Start PulumiCodeChooser -->
         ```python
         import pulumi
         import pulumi_newrelic as newrelic
@@ -179,14 +182,15 @@ class EntityTags(pulumi.CustomResource):
                 ),
             ])
         ```
+        <!--End PulumiCodeChooser -->
 
         ## Import
 
         New Relic One entity tags can be imported using a concatenated string of the format
 
-        `<guid>`, e.g.
+         `<guid>`, e.g.
 
-         bash
+        bash
 
         ```sh
         $ pulumi import newrelic:index/entityTags:EntityTags foo MjUyMDUyOHxBUE18QVBRTElDQVRJT058MjE1MDM3Nzk1

pulumi_newrelic/events_to_metrics_rule.py

@@ -218,6 +218,7 @@ class EventsToMetricsRule(pulumi.CustomResource):
 
         ## Example Usage
 
+        <!--Start PulumiCodeChooser -->
         ```python
         import pulumi
         import pulumi_newrelic as newrelic
@@ -227,14 +228,15 @@ class EventsToMetricsRule(pulumi.CustomResource):
             description="Example description",
             nrql="SELECT uniqueCount(account_id) AS ``Transaction.account_id`` FROM Transaction FACET appName, name")
         ```
+        <!--End PulumiCodeChooser -->
 
         ## Import
 
         New Relic Events to Metrics rules can be imported using a concatenated string of the format
 
-        `<account_id>:<rule_id>`, e.g.
+         `<account_id>:<rule_id>`, e.g.
 
-         bash
+        bash
 
         ```sh
         $ pulumi import newrelic:index/eventsToMetricsRule:EventsToMetricsRule foo 12345:34567
@@ -259,6 +261,7 @@ class EventsToMetricsRule(pulumi.CustomResource):
 
         ## Example Usage
 
+        <!--Start PulumiCodeChooser -->
         ```python
         import pulumi
         import pulumi_newrelic as newrelic
@@ -268,14 +271,15 @@ class EventsToMetricsRule(pulumi.CustomResource):
             description="Example description",
             nrql="SELECT uniqueCount(account_id) AS ``Transaction.account_id`` FROM Transaction FACET appName, name")
         ```
+        <!--End PulumiCodeChooser -->
 
         ## Import
 
         New Relic Events to Metrics rules can be imported using a concatenated string of the format
 
-        `<account_id>:<rule_id>`, e.g.
+         `<account_id>:<rule_id>`, e.g.
 
-         bash
+        bash
 
         ```sh
         $ pulumi import newrelic:index/eventsToMetricsRule:EventsToMetricsRule foo 12345:34567

pulumi_newrelic/get_account.py

@@ -82,12 +82,14 @@ def get_account(account_id: Optional[int] = None,
 
     ## Example Usage
 
+    <!--Start PulumiCodeChooser -->
     ```python
     import pulumi
     import pulumi_newrelic as newrelic
 
     acc = newrelic.get_account(scope="global")
     ```
+    <!--End PulumiCodeChooser -->
 
 
     :param int account_id: The account ID in New Relic.
@@ -120,12 +122,14 @@ def get_account_output(account_id: Optional[pulumi.Input[Optional[int]]] = None,
 
     ## Example Usage
 
+    <!--Start PulumiCodeChooser -->
     ```python
     import pulumi
     import pulumi_newrelic as newrelic
 
     acc = newrelic.get_account(scope="global")
     ```
+    <!--End PulumiCodeChooser -->
 
 
     :param int account_id: The account ID in New Relic.

pulumi_newrelic/get_alert_policy.py

@@ -66,7 +66,7 @@ class GetAlertPolicyResult:
     @pulumi.getter(name="incidentPreference")
     def incident_preference(self) -> Optional[str]:
         """
-        The rollup strategy for the policy. Options include: PER_POLICY, PER_CONDITION, or PER_CONDITION_AND_TARGET. The default is PER_POLICY.
+        The rollup strategy for the policy, which can have one of the following values:
         """
         return pulumi.get(self, "incident_preference")
 
@@ -107,7 +107,7 @@ def get_alert_policy(account_id: Optional[int] = None,
 
 
     :param int account_id: The New Relic account ID to operate on.  This allows you to override the `account_id` attribute set on the provider. Defaults to the environment variable `NEW_RELIC_ACCOUNT_ID`.
-    :param str incident_preference: The rollup strategy for the policy. Options include: PER_POLICY, PER_CONDITION, or PER_CONDITION_AND_TARGET. The default is PER_POLICY.
+    :param str incident_preference: The rollup strategy for the policy, which can have one of the following values:
     :param str name: The name of the alert policy in New Relic.
     """
     __args__ = dict()
@@ -136,7 +136,7 @@ def get_alert_policy_output(account_id: Optional[pulumi.Input[Optional[int]]] =
 
 
     :param int account_id: The New Relic account ID to operate on.  This allows you to override the `account_id` attribute set on the provider. Defaults to the environment variable `NEW_RELIC_ACCOUNT_ID`.
-    :param str incident_preference: The rollup strategy for the policy. Options include: PER_POLICY, PER_CONDITION, or PER_CONDITION_AND_TARGET. The default is PER_POLICY.
+    :param str incident_preference: The rollup strategy for the policy, which can have one of the following values:
     :param str name: The name of the alert policy in New Relic.
     """
     ...

pulumi_newrelic/get_application.py

@@ -86,6 +86,7 @@ def get_application(name: Optional[str] = None,
 
     ## Example Usage
 
+    <!--Start PulumiCodeChooser -->
     ```python
     import pulumi
     import pulumi_newrelic as newrelic
@@ -106,6 +107,7 @@ def get_application(name: Optional[str] = None,
             time_function="all",
         )])
     ```
+    <!--End PulumiCodeChooser -->
 
 
     :param str name: The name of the application in New Relic.
@@ -132,6 +134,7 @@ def get_application_output(name: Optional[pulumi.Input[str]] = None,
 
     ## Example Usage
 
+    <!--Start PulumiCodeChooser -->
     ```python
     import pulumi
     import pulumi_newrelic as newrelic
@@ -152,6 +155,7 @@ def get_application_output(name: Optional[pulumi.Input[str]] = None,
             time_function="all",
         )])
     ```
+    <!--End PulumiCodeChooser -->
 
 
     :param str name: The name of the application in New Relic.

pulumi_newrelic/get_authentication_domain.py

@@ -60,6 +60,7 @@ def get_authentication_domain(name: Optional[str] = None,
 
     ## Example Usage
 
+    <!--Start PulumiCodeChooser -->
     ```python
     import pulumi
     import pulumi_newrelic as newrelic
@@ -67,6 +68,7 @@ def get_authentication_domain(name: Optional[str] = None,
     foo_authentication_domain = newrelic.get_authentication_domain(name="Test Authentication Domain")
     pulumi.export("foo", foo_authentication_domain.id)
     ```
+    <!--End PulumiCodeChooser -->
 
 
     :param str name: The name of the authentication domain to be searched for. An error is thrown, if no authentication domain is found with the specified name.
@@ -89,6 +91,7 @@ def get_authentication_domain_output(name: Optional[pulumi.Input[str]] = None,
 
     ## Example Usage
 
+    <!--Start PulumiCodeChooser -->
     ```python
     import pulumi
     import pulumi_newrelic as newrelic
@@ -96,6 +99,7 @@ def get_authentication_domain_output(name: Optional[pulumi.Input[str]] = None,
     foo_authentication_domain = newrelic.get_authentication_domain(name="Test Authentication Domain")
     pulumi.export("foo", foo_authentication_domain.id)
     ```
+    <!--End PulumiCodeChooser -->
 
 
     :param str name: The name of the authentication domain to be searched for. An error is thrown, if no authentication domain is found with the specified name.

pulumi_newrelic/get_cloud_account.py

@@ -81,6 +81,7 @@ def get_cloud_account(account_id: Optional[int] = None,
 
     ## Example Usage
 
+    <!--Start PulumiCodeChooser -->
     ```python
     import pulumi
     import pulumi_newrelic as newrelic
@@ -89,6 +90,7 @@ def get_cloud_account(account_id: Optional[int] = None,
         cloud_provider="aws",
         name="my aws account")
     ```
+    <!--End PulumiCodeChooser -->
 
 
     :param int account_id: The account ID in New Relic.
@@ -120,6 +122,7 @@ def get_cloud_account_output(account_id: Optional[pulumi.Input[Optional[int]]] =
 
     ## Example Usage
 
+    <!--Start PulumiCodeChooser -->
     ```python
     import pulumi
     import pulumi_newrelic as newrelic
@@ -128,6 +131,7 @@ def get_cloud_account_output(account_id: Optional[pulumi.Input[Optional[int]]] =
         cloud_provider="aws",
         name="my aws account")
     ```
+    <!--End PulumiCodeChooser -->
 
 
     :param int account_id: The account ID in New Relic.

pulumi_newrelic/get_entity.py

@@ -146,12 +146,40 @@ def get_entity(account_id: Optional[int] = None,
     """
     Use this data source to get information about a specific entity in New Relic One that already exists.
 
-    ## Additional Examples
+    ### Example: Filter By Account ID
 
-    > If the entities are not found please try again without providing the `type` field.
+    The default behaviour of this data source is to retrieve entities matching the specified parameters (such as `name`, `domain`, `type`) from NerdGraph with the credentials specified in the configuration of the provider (account ID and API Key), filter them by the account ID specified in the configuration of the provider, and return the first match.
 
+    This would mean, if no entity with the specified search parameters is found associated with the account ID in the configuration of the provider, i.e. `NEW_RELIC_ACCOUNT_ID`, an error is thrown, stating that no matching entity has been found.
+
+    <!--Start PulumiCodeChooser -->
+    ```python
+    import pulumi
+    import pulumi_newrelic as newrelic
+
+    app = newrelic.get_entity(domain="APM",
+        name="my-app",
+        type="APPLICATION")
+    ```
+    <!--End PulumiCodeChooser -->
+    However, in order to cater to scenarios in which it could be necessary to retrieve an entity belonging to a subaccount using the account ID and API Key of the parent account (for instance, when entities with identical names are present in both the parent account and subaccounts, since matching entities from subaccounts too are returned by NerdGraph), the `account_id` attribute of this data source may be availed. This ensures that the account ID in the configuration of the provider, used to filter entities returned by the API is now overridden by the `account_id` specified in the configuration; i.e., in the below example, the data source would now return an entity matching the specified `name`, belonging to the account with the ID `account_id`.
+    <!--Start PulumiCodeChooser -->
+    ```python
+    import pulumi
+    import pulumi_newrelic as newrelic
+
+    app = newrelic.get_entity(account_id=654321,
+        domain="APM",
+        name="my-app",
+        type="APPLICATION")
+    ```
+    <!--End PulumiCodeChooser -->
+    The following example explains a use case along the lines of the aforementioned; using the `account_id` argument in the data source to allow the filtering criteria to be the `account_id` specified (of the subaccount), and not the account ID in the provider configuration.
+
+    In simpler terms, when entities are queried from the parent account, entities with matching names are returned from subaccounts too, hence, specifying the `account_id` of the subaccount in the configuration allows the entity returned to belong to the subaccount with `account_id`.
     ### Query for an OTEL entity
 
+    <!--Start PulumiCodeChooser -->
     ```python
     import pulumi
     import pulumi_newrelic as newrelic
@@ -164,9 +192,11 @@ def get_entity(account_id: Optional[int] = None,
         )],
         type="SERVICE")
     ```
+    <!--End PulumiCodeChooser -->
 
     ### Query for an entity by type (AWS Lambda entity in this example)
 
+    <!--Start PulumiCodeChooser -->
     ```python
     import pulumi
     import pulumi_newrelic as newrelic
@@ -174,6 +204,7 @@ def get_entity(account_id: Optional[int] = None,
     app = newrelic.get_entity(name="my_lambda_trace",
         type="AWSLAMBDAFUNCTION")
     ```
+    <!--End PulumiCodeChooser -->
 
 
     :param int account_id: The New Relic account ID the entity to be returned would be associated with, i.e. if specified, the data source would filter matching entities received by `account_id` and return the first match. If not, matching entities are filtered by the account ID specified in the configuration of the provider. See the **Example: Filter By Account ID** section above for more details.
@@ -217,12 +248,40 @@ def get_entity_output(account_id: Optional[pulumi.Input[Optional[int]]] = None,
     """
     Use this data source to get information about a specific entity in New Relic One that already exists.
 
-    ## Additional Examples
+    ### Example: Filter By Account ID
 
-    > If the entities are not found please try again without providing the `type` field.
+    The default behaviour of this data source is to retrieve entities matching the specified parameters (such as `name`, `domain`, `type`) from NerdGraph with the credentials specified in the configuration of the provider (account ID and API Key), filter them by the account ID specified in the configuration of the provider, and return the first match.
+
+    This would mean, if no entity with the specified search parameters is found associated with the account ID in the configuration of the provider, i.e. `NEW_RELIC_ACCOUNT_ID`, an error is thrown, stating that no matching entity has been found.
+
+    <!--Start PulumiCodeChooser -->
+    ```python
+    import pulumi
+    import pulumi_newrelic as newrelic
+
+    app = newrelic.get_entity(domain="APM",
+        name="my-app",
+        type="APPLICATION")
+    ```
+    <!--End PulumiCodeChooser -->
+    However, in order to cater to scenarios in which it could be necessary to retrieve an entity belonging to a subaccount using the account ID and API Key of the parent account (for instance, when entities with identical names are present in both the parent account and subaccounts, since matching entities from subaccounts too are returned by NerdGraph), the `account_id` attribute of this data source may be availed. This ensures that the account ID in the configuration of the provider, used to filter entities returned by the API is now overridden by the `account_id` specified in the configuration; i.e., in the below example, the data source would now return an entity matching the specified `name`, belonging to the account with the ID `account_id`.
+    <!--Start PulumiCodeChooser -->
+    ```python
+    import pulumi
+    import pulumi_newrelic as newrelic
+
+    app = newrelic.get_entity(account_id=654321,
+        domain="APM",
+        name="my-app",
+        type="APPLICATION")
+    ```
+    <!--End PulumiCodeChooser -->
+    The following example explains a use case along the lines of the aforementioned; using the `account_id` argument in the data source to allow the filtering criteria to be the `account_id` specified (of the subaccount), and not the account ID in the provider configuration.
 
+    In simpler terms, when entities are queried from the parent account, entities with matching names are returned from subaccounts too, hence, specifying the `account_id` of the subaccount in the configuration allows the entity returned to belong to the subaccount with `account_id`.
     ### Query for an OTEL entity
 
+    <!--Start PulumiCodeChooser -->
     ```python
     import pulumi
     import pulumi_newrelic as newrelic
@@ -235,9 +294,11 @@ def get_entity_output(account_id: Optional[pulumi.Input[Optional[int]]] = None,
         )],
         type="SERVICE")
     ```
+    <!--End PulumiCodeChooser -->
 
     ### Query for an entity by type (AWS Lambda entity in this example)
 
+    <!--Start PulumiCodeChooser -->
     ```python
     import pulumi
     import pulumi_newrelic as newrelic
@@ -245,6 +306,7 @@ def get_entity_output(account_id: Optional[pulumi.Input[Optional[int]]] = None,
     app = newrelic.get_entity(name="my_lambda_trace",
         type="AWSLAMBDAFUNCTION")
     ```
+    <!--End PulumiCodeChooser -->
 
 
     :param int account_id: The New Relic account ID the entity to be returned would be associated with, i.e. if specified, the data source would filter matching entities received by `account_id` and return the first match. If not, matching entities are filtered by the account ID specified in the configuration of the provider. See the **Example: Filter By Account ID** section above for more details.