This message was deleted.

sparse-intern-71089

02/10/2021, 9:37 PM

This message was deleted.

little-cartoon-10569

02/10/2021, 9:39 PM

My recommendation is: 1) all config should be accessed only in your Pulumi program (index.ts, or your language's equivalent), and 2) only unit test your ComponentResources. This avoids all complexities like you describe.

little-cartoon-10569

02/10/2021, 9:40 PM

Move all your unit-testable code into resources and test those. There should be next to no logic in the top-level file (index.ts or whatever). Any logic in there can be tested using integration / system level testing.

fast-oyster-42706

02/10/2021, 9:45 PM

I am only testing a single function that creates a resource group and storage account (azure). So I guess you are saying I should move the reading of the config value out of that function? Just trying think through how this should look.

little-cartoon-10569

02/10/2021, 9:46 PM

Yes. Pass in the value, from both the program and the unit test.

little-cartoon-10569

02/10/2021, 9:47 PM

That's a good practice in any language or framework. Minimize dependencies within each function. If a function does a thing, it shouldn't get-config-then-do-thing.

fast-oyster-42706

02/10/2021, 9:47 PM

Ok seems to make sense. Thanks will give it a try.

👍 1

47 Views

Open in Slack

Previous Next

Pulumi Community

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.