And, from what I've seen, once you have pulumi itself, it tends to grab the modules it depends on by itself

Ugh, git is not a good place for binary files

git releases?

https://github.blog/2013-07-02-release-your-software/ I think this is designed specifically for bins

So it doesn't go into your typical git workflow

But that's not "bins would be in git"

Right, yeah

I guess right now I do store bins in git, but it's temporary

But anyway, pulumi "installer" just grabs tarball, extracts under

~/.pulumi/bin/

and adds that to path. If you take care of

$PATH

, you could probably just have it inside tarred up project dir

I'll still have to take care of installing the dependencies, which is fine I suppose

docker is starting to feel like the simplest solution

There appears to be https://www.npmjs.com/package/pkg for something like that, or there AppImage

Yeah, I've been trying to get pkg working with aws-cdk. I'm hoping it'll be simpler with pulumi

https://docs.appimage.org/packaging-guide/manual.html#ref-manual 🤷

Welcome to the wonderful world of software distribution ;)

On the other other other hand, there's https://fpm.readthedocs.io/en/latest/intro.html

Oh yeah, I've used fpm before, forgot about that

but I don't want to install 'things' on people's systems

the idea is to just get an aws env set up

but saying "Install docker first" is probably the best I can do

Hi, would anyone know some articles on how to organise infra and deployments into projects and stacks? specifically talking about a general purpose k8s kluster for our organisation that would need to host multiple deployments of application services. I’ve read (somewhere) a pulumi stack can pull in infrastructure managed in a different repository, which sound what I would need…

Hi all, I'm considering writing a custom provider but wonder whether this has to be written in Go or if that's also possible in TypeScript and if so if there is an example of a TS based provider. I used dynamic providers previously but feel that they are not really reusable across projects...

I’m experiencing pretty slow

pulumi up

runs (even during preview phase) with a project containing two `StackReference`s. It’s hanging on

running     read pulumi:pulumi:StackReference ajaegle/proj/stack

for ages and the super verbose log doesn’t list any more lines than the ones that were there since the beginning (the diff of some resources). I don’t expect that to be lossy internet connectivity as my machine is constantly using almost two cores for the pulumi process.

I have a chicken and the egg kind of question. Let’s say that you have some applications that you want to run on a kubernetes cluster. The images should be published to a registry first and that is something I would like to do during build, but the registry isn’t created until deployment. Is there a best practice here? Setting up the registry in its own project?

Is there a way to create an object that only exists to get a name with a suffix (to break circular dependencies)? If you want to make a storage container that's only accessible from a web app that knows the name of that storage container, then you need to make the container with a CORS rule that knows the URL of the web app, but the web app needs to know the deployed name of the container. If you can create a placeholder resource that gets the suffix added to its ID, then the web app can be given the ID, and the container can then be created with that name and a CORS rule with the URL of the web app. like:

let containerIdHolder = CustomResource("justAName", "mycontainer", ResourceArgs.Empty)
...
let envVars = Inputs.ServiceTemplateSpecContainersEnvsArgs(Name = "containerName", Value = containerIdHolder.Id)
...
let webApp = WebApp (envVars = ["containerName", containerIdHolder.Id)]) 
...
let actualContainer = Container (Name = containerIdHolder.Id, CorsRules = (Origins = [webApp.url]))

Is that possible?

https://onalytica.com/blog/posts/top-100-cloud-influencers/?ck_subscriber_id=512829154 Wow Joe is 23rd ❗

until the bug with

runtime.listResourceOutputs

is fixed, are there any suggestions from folks on what i could use in the interim? i'm using it to, if no resource X has ever been deployed, deploy it, otherwise, use what's already deployed.

Deployment name is appended with random chars when used like this - https://github.com/grendach/pulumi-quickstart/blob/61911bc3cb2464c58c4e64d75a1c0e0980e40d79/__main__.py#L14 -- Any tip to fix it ?

Is there a way to have global value with stacks? I don’t want to copy the same value in my multiple stack?