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

Does this work?

```
function getRuleByName(name: string)     {
    return pulumi.all(nsg.rules.map(r =&gt; r.rule.name)).apply(ruleNames =&gt; {
        return ruleNames.find(ruleName =&gt; name === ruleName);
    });
}
```

`nsg.rules` is of type `NetworkSecurityRule[]`, `NetworkSecurityRule` being a custom ComponentResource and has a `rule` property of type `azure.network.NetworkSecurityRule`.

Thank you for your help <@UB3BGTV63>.
This only outputs the name of the rules, instead of the rules object.

I'm still stuck on this :
<https://pulumi-community.slack.com/archives/CJ909TL6P/p1572375960100600>
Anybody has any suggestion, please ?

You should export Outputs directly, potentially changed with `apply` and `all`

So something like Luke suggested but without mapping to name first

Thanks for your help <@UB39JFCKC>
The `Promise()` is just to unwrap the underlying object from the output, as explained in this article :
<https://www.pulumi.com/blog/unit-testing-infrastructure-in-nodejs-and-mocha/>
As per your suggestion, i modified `getRuleByName` like so :

```
function getRuleByName(name: string) {
    return pulumi.all(nsg.rules.apply(r =&gt; {
        return r.find(r =&gt; r.rule.name === name)
    })
}```
But then I get the error :
`Property 'apply' does not exist on type 'NetworkSecurityRule[]'.`

`NetworkSecurityRule` is a custom ComponentResource which contains an `azure.network.NetworkSecurityRule.`

Should be `return pulumi.all(nsg.rules).apply(r  =&gt; ...`

Thanks <@UB39JFCKC>
So this :

```function getRuleByName(name: string) {
    return pulumi.all(nsg.rules).apply(r => {
        return r.find(r => r.rule.name === name)
    })
}```
Results in the following error for the test in the find method:
`This condition will always return 'false' since the types 'Output<string>' and 'string' have no overlap`

And this might work :

```function getRuleByName(name: string) {
    return pulumi.all(nsg.rules).apply(r =&gt; {
        return r.find(r =&gt; r.rule.name.get() === name)
    })
}```
But it result in the following error :

```Error: Cannot call '.get' during update or preview.
    To manipulate the value of this Output, use '.apply' instead.```


Sorry for many false hints. Now I finally opened an editor and this seems to fit your use case:
```
function getRuleByName(name: string) {
  return pulumi.all(nsg.rules.map(r =&gt; r.name)).apply(names =&gt; {
      const index = names.indexOf(name);
      return index &gt;= 0 ? nsg.rules[index] : undefined;
  });
}```

<@UB39JFCKC> Wow, that is some ugly and convoluted code, but it works !
I remember seeing a Github issue related to making outputs easier to deal with, but I cannot find it.
I think that outputs should be simpler to use.
A common use case is testing : importing the outputs into the tests suite and running assertions against them should be much simpler than it is now.
Anyway, thanks a lot for your help.

That's a valid but a challenging goal. I'm glad you are unblocked for now.