pulumi-community #contribute

Join the conversation Join Slack

contribute

microscopic-dusk-80789

03/21/2019, 1:57 AM

can the project guarantee that ? 😛

stocky-spoon-28903

03/21/2019, 1:57 AM

Not really - the intended use is for the

pulumi

CLI to be the entry point

stocky-spoon-28903

03/21/2019, 1:57 AM

It’s generally not proven necessary to wrap it with anything

stocky-spoon-28903

03/21/2019, 1:57 AM

If you want to look at embedding, the best place to start is in the

pulumi/pulumi

repo, at the command implementation for the

up

command

microscopic-dusk-80789

03/21/2019, 1:58 AM

the thing I want to build is for ppl who dont know what a terminal is and have never heard the word CLI before

microscopic-dusk-80789

03/21/2019, 1:58 AM

thats why I want to wrap it

microscopic-dusk-80789

03/21/2019, 1:58 AM

Its unreasonable to ask my intended users to open a terminal.

stocky-spoon-28903

03/21/2019, 1:59 AM

https://github.com/pulumi/pulumi/blob/master/cmd/up.go is the entry point you’re looking for

microscopic-dusk-80789

03/21/2019, 1:59 AM

Yeah, I think Ive already gone a ways down this path, but i'm lost 😛

stocky-spoon-28903

03/21/2019, 1:59 AM

Like I say, there is no API stability guarantee for the internals, so I wouldn’t be surprised if it breaks on a regular basis!

stocky-spoon-28903

03/21/2019, 1:59 AM

In general, you’ll need to hook the engine into two other things: the language host and the resource provider plugins

microscopic-dusk-80789

03/21/2019, 2:00 AM

let me look at what I have so far and you can tell my how wildly off base I am

stocky-spoon-28903

03/21/2019, 2:01 AM

FWIW as far as I know no-one has yet tried doing this - certainly I haven’t 🙂

microscopic-dusk-80789

03/21/2019, 2:02 AM

yeah thats what it looked like to me too after some googling but im willing to give it a shot

microscopic-dusk-80789

03/21/2019, 2:02 AM

so I made a new

filestate

, then I tried to create a

pulumi.RunInfo

and call

pulumi.NewContext

on it, then finally call

pulumi.RunWithContext

with my

pulumiContext

and

RunFunc

(program)

microscopic-dusk-80789

03/21/2019, 2:03 AM

the RunInfo has two addresses for servers,

MonitorAddr

and

EngineAddr

microscopic-dusk-80789

03/21/2019, 2:03 AM

just now I was playing around with spawning the pulumi-language-go process -- I thought that was the

engine

grpc server I was looking for at 1st

microscopic-dusk-80789

03/21/2019, 2:03 AM

but then I looked closer and the

pulumi-language-go

also connects to something called

engine

stocky-spoon-28903

03/21/2019, 2:04 AM

pulumi-language-go is the runtime for go programs, not the engine

microscopic-dusk-80789

03/21/2019, 2:04 AM

so, obviously im missing something here. I'll probably just have to run through it in the debugger when invoking it from the command line and watch wat it does

stocky-spoon-28903

03/21/2019, 2:04 AM

The runtime makes RegisterResource RPC calls to the engine whenever objects are instantiated in the program

microscopic-dusk-80789

03/21/2019, 2:05 AM

so, let me zoom out a bit

microscopic-dusk-80789

03/21/2019, 2:05 AM

pulumi CAN run with just the cli right?

microscopic-dusk-80789

03/21/2019, 2:06 AM

so, the scope of what I am looking for is contained for the most part in the

pulumi/pulumi

repo

microscopic-dusk-80789

03/21/2019, 2:06 AM

is there an architechtural diagram of how the CLI works ?

microscopic-dusk-80789

03/21/2019, 2:07 AM

it looks like it spawns multiple servers which talk to each-other over GRPC in order to do its job

microscopic-dusk-80789

03/21/2019, 2:07 AM

and then it can optionally talk to some server that the pulumi company runs, presumably to store your state for you safely and securely

stocky-spoon-28903

03/21/2019, 2:07 AM

Actually I think there is a video explaining it somewhere

microscopic-dusk-80789

03/21/2019, 2:07 AM

is there a pulumi Daemon or something that the CLI is a client of ?

stocky-spoon-28903

03/21/2019, 2:08 AM

https://www.youtube.com/watch?v=YMAe59BYzm4▾