https://pulumi.com logo
n

nutritious-grass-41895

10/19/2018, 7:49 PM
Can i tell pulumi to fetch the configs from a git repo url directly ? in a multi repo case for example ?
c

creamy-potato-29402

10/19/2018, 7:50 PM
@nutritious-grass-41895 what do you mean by “configs”? Like, YAML files?
n

nutritious-grass-41895

10/19/2018, 7:51 PM
Not really the actual pulumi code. since all the configs are basically code
c

creamy-potato-29402

10/19/2018, 7:52 PM
Hmm, I’m not quite sure I understand the use case… Can you publish them to NPM and reference them as libraries?
n

nutritious-grass-41895

10/19/2018, 7:52 PM
Apologies for not being clear here ...
Let me explain my use case
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
c

creamy-potato-29402

10/19/2018, 7:55 PM
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?
n

nutritious-grass-41895

10/19/2018, 7:55 PM
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
good .. point ..
c

creamy-potato-29402

10/19/2018, 7:56 PM
So for example imagine something like this:
Copy code
import {deployment, serviceAccount} from "my-frontend"
that seems like it ought to work.
n

nutritious-grass-41895

10/19/2018, 7:57 PM
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
c

creamy-potato-29402

10/19/2018, 8:00 PM
Yeah, me too.
n

nutritious-grass-41895

10/19/2018, 8:00 PM
Some of the repos source code have actual source script that would need to be published with the pulumi code as well
c

creamy-potato-29402

10/19/2018, 8:00 PM
But yes, it’s pretty much the same.
yes, makes sense.