I am often struggling to write reusable code and I think im doing something wrong. For example right now im provisioning a second database and migrating the main one to it. Something that could've been 3 lines of code ended up forcing me to copy paste a bunch of methods or add parameters because every resource URN ended up being a duplicate (including passwords). There should be a better way of doing this, but with the length limitations im struggling to find a good convention for URNs that can be done programatically (eg concatenating a couple of parameters).

Can you share some code? You shouldn't be seeing duplicate urns

The duplicate URNs are because im kinda manually setting them. I usually concatenate a couple of properties from the parameters and append some string to them, but in some scenarios I need to further differentiate. I was just wondering if I can follow some common rules of thumb so I can make my infra setup a bit more reusable. Eg creating the same schema in the {environment} database and in the {environment-just-doing-some-test} database gets quite complex as a lot of stuff is involved

How come you're not letting Pulumi handle the naming for you?

I use pulumi's naming for things most things like resource groups or storage accounts, but not for db schemas or user accounts

Sorry, yes you're right about the name there needing to be unique