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

No. You might use 2 projects for that, and a StackReference to share information from the "prepare" project to the "configure" project.
Or else maintain a record of the specific logs to enable yourself, and enable them in the same step as you're creating it? If feasible, this is definitely easier, and it ensures you've got predictable state after Pulumi completes.

Alternatively, you should be able to do that with the Automation API, which gives you a lot more fine-grained control over operation ordering. <https://www.pulumi.com/blog/automation-api/>