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

<@UDH9GBDME> what do you mean by “configs”? Like, YAML files?

Not really the actual pulumi code. since all the configs are basically code

Hmm, I’m not quite sure I understand the use case… Can you publish them to NPM and reference them as libraries?

i have three repos defining a single application for example `{frontend,app,db}` ..

if i have a single pulumi project that would reference these three repos that would be good

I see. Is there a reason you don’t want each of these apps to be a library, that you publish to NPM, and which the single Pulumi project uses?

the waork around would be to to git submodules and fetch all repose as if they were all in the same repo and make pulumi think that it was a single repo when deploying all

So for example imagine something like this:

```
import {deployment, serviceAccount} from "my-frontend"
```

it should although i am more a go/java lang person than npm. but the circuitry would be the same

so the required extra step would be to treat the infrastructure code as an artifact to publish first

Some of the repos source code have actual source script that would need to be published with the pulumi code as well