Hello. I've been testing the .net client over the last 24 hours to see if it's suitable to replace our ARM templates. It's going pretty well, but I have two questions:
1. How do people deal with the random AppService naming? The rest I get, but the name of the appservice also drives the URL it runs under, which has flow-on effects to stuff like custom domains, CORS policies, auth integration etc. Does every single person that uses Pulumi for app service deployment override the naming convention?
2. Currently we share a single resource group between our front-end and back-end arm templates, with the RG being created via the az command line if it doesn't exist already. How should this be represented within a Pulumi definition (considering we still want the stack definitions to remain separate between our front-end and back-end)?