No matter how you like to participate in developer communities, Pulumi wants to meet you there. If you want to meet other Pulumi users to share use-cases and best practices, contribute code or documentation, see us at an event, or just tell a story about something cool you did with Pulumi, you are part of our community.

Pulumi Community

One way of fixing this would be to instantiate a new
``` AzureNative.Storage.StorageAccount```
 with a pulumi ID from a different stack. Can it be done?

.. or am I forced to create the Storage account, vnet and the rule all at once in one stack? :rage:

Unfortunately we don’t have a great answer for partial updates right now… I think there’s no issue tracking this particular scenario - could you please add one?

Thank you for answering. I will fill out an issue on github next monday. (I prefer working with pulumi on weekdays).