Sorry I don't get the comment. Pulumi is meant to read secrets from one KeyVault and copy it to various ones across multiple KeyVauls which are in different Azure Subscription. I don't have an issue with KeyVault secret handling but creating the provider configuration to access the KeyVaults. I want fully control which provider is used when I access any KeyVault.
kind-afternoon-60990
07/12/2023, 3:26 AM
The source secret is is done manually, the target ones obviously via pulumi. But to access the KeyVault to read the secret I need already a provider configuration
kind-afternoon-60990
07/12/2023, 3:27 AM
For now I don't have any secrets, I struggle to configure the provider itself. As "hello world" I try to just display all resources in a resource group in a target subscription.
kind-afternoon-60990
07/12/2023, 3:29 AM
I just gave the use-case above to explain why I need to work across subscriptions. Actually I have many other use-cases that require the same.
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.