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

yeah so a bit of both. I envision having a single repo with a multimodule gradle project
```rootProject.name = "pulumi"
include(
    "libs:modules",
    "services:app-cluster",
    "services:mgmt-cluster",
    "testing:commons",
)```

I think the issue is that it runs gradle local to each service so its not picking up general stuff thats defined in the root project

like is it not picking up a pulumi config file?

E.g. im  using <https://docs.gradle.org/current/userguide/platforms.html>, a toml file where i define versions and refer them in the projects as
```dependencies {
    implementation(libs.groovy.core)
}```
And this just fails as it cant resolve it

Also using  `buildSrc` which also doesnt work to refer in the `build.gradle` file inside of the services folder

I believe its because its running just `gradle` locally from the folder instead of actually invoking gradle with the service from the root of the repository,
i.e. `gradle :services:app-cluster`

The dir structure (simplified):
```settings.gradle
build.gradle
services/
  -&gt; app-cluster/
       * build.gradle
       * Pulumi.yaml
       * Pulumi.dev.yaml
       * Pulumi.staging.yaml
       * Pulumi.production.yaml
   -&gt; mgmt-cluster/
       * build.gradle
       * Pulumi.yaml
       * Pulumi.dev.yaml
       * Pulumi.staging.yaml
       * Pulumi.production.yaml```


I’d be interested in making this work could you file an issue? It’d be a relatively simple change to teach `pulumi-language-java` how to invoke gradle from the right folder and with the right args.

<https://github.com/pulumi/pulumi-java/issues>

So I'm still in pulumi python land, but one thing we're doing is running everything through a separate wrapper script that sets some env vars and points to the appropriate command line.

One thing you could maybe do is create a cradle task that executes the pulumi cli with appropriate args and from the appropriate directory 

Yeah sure ill create an issue :slightly_smiling_face:

<https://github.com/pulumi/pulumi-java/issues/576>

Let me know if you need me to try anything out, would love to get this working so we can migrate from typescript and have everything in kotlin