Hey everyone. Seems like Pulumi’s auto-naming feat...
# general
s
Hey everyone. Seems like Pulumi’s auto-naming feature uses URNs of the resource name to generate the random string. So these URNs are of the format:
urn:pulumi:{stack-name}::{project-name}::{provider}:resources:{resource-type}::{resource-name}
Example URN:
urn:pulumi:dev::azure-ts-functions-many::azure-native:resources:ResourceGroup::windowsrg
Therefore, it seems to generate the same random string if run with the same project and stack name. Is this the ideal and expected behaviour? Facing issues for global resources when trying to deploy example projects with common stack names.
b
I think we’re aware of this, checking
d
I just got surprised by this too - I deleted all my azure resources, among them a key vault - which of course was only soft deleted (that's ok). When I re-create everything I get a complaint from Azure about keys already existing.
which just demonstrates that this is happening for me too - no concern from my side at this stage, i've got it under control.
p
Not sure if it directly addresses this, but the doc page Resource Names is pretty good.
b
@stocky-helmet-82003 we are fixing this in the next release, standby
💪 1
🙌 1