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

Hi, pulumi yaml 1.11 release breaks our custom compiler usage. We have multiple yamls which we include inside the compiler and output final yaml for pulumi, it was fine before 1.11 but now we have `failed to discover plugin requirements: searching . for package declarations` Perhaps because now Pulumi scans every yaml (even in nested directories) from <https://github.com/pulumi/pulumi-yaml/blob/main/pkg/server/server.go#L79|here> and <https://github.com/pulumi/pulumi-yaml/blob/main/pkg/pulumiyaml/run.go#L95|here>. So, it seems no possible to have custom yamls now inside the project. Any workaround? How we can configure Pulumi to ignore custom yamls?