This message was deleted.
# generals
sparse-intern-71089
11/13/2019, 5:08 AMThis message was deleted.
b
broad-dog-22463
11/13/2019, 5:49 AMHi @adventurous-garage-59192
So you can use the Pulumi/random provider as part of your Pulumi scripts and it will take care of randomness
When it comes to passing a stack name then I’d suggest a passing a resource group name via the CLi and Pulumi config
Paul
a
adventurous-garage-59192
11/13/2019, 6:07 AMHi Paul, thanks for the response, but I'm unsure what you mean by using the random provider. I'm talking about the postfix added to the end of created resources, per https://github.com/pulumi/pulumi/issues/1518.
Passing the RG name into the config does make sense, cheers.
t
tall-librarian-49374
11/13/2019, 10:19 AM@adventurous-garage-59192 you can set
Nametall-librarian-49374
11/13/2019, 10:22 AMRe Q2 - The Pulumi way is to create e.g. three stacks - one with common resources (RG), one for backend, one for frontend. Now, stack references aren't working for .NET yet, so you'd have to fix (in code or configs) the name of the resource group for now.
a
adventurous-garage-59192
11/13/2019, 10:59 AMI'm aware I can set the name property, I'm just wondering if that's what people normally do considering this is the standard behavior. Having a postfix on regularly used Dev/Test/Prod AppService environments just seems like an unusable scenario.
And yep, I assumed I would need to do something like that. Hardcoding the RG isn't a problem for the next few months.
t
tall-librarian-49374
11/13/2019, 12:48 PMYeah, I understand what you mean. I can only refer you to https://www.pulumi.com/docs/intro/concepts/programming-model/#autonaming for now
tall-librarian-49374
11/13/2019, 12:48 PMMaybe some resources could default to fixed names but then we should be careful to make it predictable somehow
tall-librarian-49374
11/13/2019, 12:49 PMI used App Services with generated names behind a Traffic Manager - that's where auto naming served just fine