This message was deleted.

Hi Igor, great to see you here!

SecurityRule

is a resource while

SecurityRuleArgs

is its input type, they aren’t the same thing. When building a list of args, you should pass args objects. E.g. this will compile:

var ruleArgs1 = new Pulumi.AzureNextGen.Network.Latest.SecurityRuleArgs
{
    SecurityRuleName = "RDP_3389",
    //...
};
var ruleArgs2 = new Pulumi.AzureNextGen.Network.Latest.SecurityRuleArgs
{
    SecurityRuleName = "Port_6516",
    //...
};
var securityRules = new List<Pulumi.AzureNextGen.Network.Latest.SecurityRuleArgs> { ruleArgs1, ruleArgs2 };

ok, so no need to create rules to get that list for NSG?

Azure’s Network resource provider is designed somewhat confusingly. You can either set rules inside the property of NSG or define them as separate resources. If you go for the former option, you only need

args

. If you choose the latter, you create several

SecurityRule

resources but do not pass them to NSG.

I don't see how those rules will get proper names then 🙂, will try and see

You can set

Name

in both cases, can’t you?

had to rewrite that piece:

var rule1Args = new Pulumi.AzureNextGen.Network.Latest.Inputs.SecurityRuleArgs

        {             Access = "Allow", //Deny, Allow             //...         };         var rule2Args = new Pulumi.AzureNextGen.Network.Latest.Inputs.SecurityRuleArgs         {             Access = "Allow", //Deny, Allow             //...         };         var securityRulesArgs = new List<Pulumi.AzureNextGen.Network.Latest.Inputs.SecurityRuleArgs> { rule1Args, rule2Args };         var nsg = new NetworkSecurityGroup("nsg", new Pulumi.AzureNextGen.Network.Latest.NetworkSecurityGroupArgs         {             Location = _resourceGroup.Location,             ResourceGroupName = _resourceGroup.Name,             NetworkSecurityGroupName = "nsg",             SecurityRules = securityRulesArgs,         });

right, now it worked, before VSCode was complaining...