No matter how you like to participate in developer communities, Pulumi wants to meet you there. If you want to meet other Pulumi users to share use-cases and best practices, contribute code or documentation, see us at an event, or just tell a story about something cool you did with Pulumi, you are part of our community.

Pulumi Community

Not with resources, but some providers give functions that are a bit more flexible.

For anomalies in Azure, the Azure Native provider has the `getanomalies` function, though this doesn't seem available in the Classic provider.
<https://www.pulumi.com/registry/packages/azure-native/api-docs/securityinsights/getanomalies/>

hm, but that seems to return the found anomalies

Usually if I need flexibility, I'll use other libraries along with Pulumi. Power of using a real language is you're not locked into _just_ using the framework :wink:

yeah, but our problem is with pulumi directly, cause anomaly detector can be defined just once, but its being recreated on many occassions causing deployment to fail

being able to look up its reference and use that could prevent pulumi from triggering another creation

for operations later on, sure, we use other technologies too :slightly_smiling_face:

best bet is looking for if the provider has those `get` functions that have filtering then. They generally don't require knowing a name

&gt; /// &lt;summary&gt;
&gt; /// Get an existing SmartDetectorAlertRule resource's state with the given name, ID, and optional extra
&gt; /// properties used to qualify the lookup.
&gt; /// &lt;/summary&gt;
&gt; ///
&gt; /// &lt;param name="name"&gt;The unique name of the resulting resource.&lt;/param&gt;
&gt; /// &lt;param name="id"&gt;The unique provider ID of the resource to lookup.&lt;/param&gt;
&gt; /// &lt;param name="options"&gt;A bag of options that control this resource's behavior&lt;/param&gt;
&gt; public static SmartDetectorAlertRule Get(string name, Input&lt;string&gt; id, CustomResourceOptions? options = null)
&gt; {
&gt;     return new SmartDetectorAlertRule(name, id, options);
&gt; }