pulumi-community #general

Docs

Join the conversation Join Slack

Channels

general

rough-oil-1458

09/03/2018, 5:30 PM

Most of TF modules work in Fargate also, since Triton (Joyents Cloud) was a Container based IaaS, that runs on SmartOS

rough-oil-1458

09/03/2018, 5:32 PM

so many ways to skin cats

rough-oil-1458

09/03/2018, 5:43 PM

ed, do you guys use packer?

boundless-monkey-50243

09/03/2018, 6:06 PM

No, and even if I did it would be an optimization rather than the only method of deployment

boundless-monkey-50243

09/03/2018, 6:08 PM

It's fine though, with appropriate tooling around it

boundless-monkey-50243

09/03/2018, 6:31 PM

Is there an example floating around out there of a custom resource that just composes other existing resources?

boundless-monkey-50243

09/03/2018, 6:34 PM

Aha,

aws-infra

. This is a bit hefty, but makes sense...

big-piano-35669

09/03/2018, 6:36 PM

This one's a bit simpler, though it's Kubernetes, not AWS: https://github.com/pulumi/examples/blob/master/kubernetes-ts-guestbook/components/k8sjs.ts. The

ServiceDeployment

class is a mashup of a

Deployment

and

Service

object, and is ever-so-slightly opinionated on inputs/outputs shapes.

boundless-monkey-50243

09/03/2018, 6:38 PM

Aah, this is a lot easier to read.

boundless-monkey-50243

09/03/2018, 6:38 PM

Thanks

boundless-monkey-50243

09/03/2018, 6:39 PM

I do only want it as a logical container, so that's really handy

boundless-monkey-50243

09/03/2018, 6:49 PM

Hm - my custom resource is looking for a plugin provider on my $PATH, which does not exist. Can I tell it to not do that?

boundless-monkey-50243

09/03/2018, 6:50 PM

constructor(name: string, baseArgs: NetworkArgs, opts?: pulumi.ComponentResourceOptions) {
    super("carestack:aws:components:Network", name, {}, opts);

results in

error: no resource plugin 'carestack' found in the workspace or on your $PATH

I assumed the token names were just for humans, but I guess not.

boundless-monkey-50243

09/03/2018, 6:53 PM

(I can't cheat and name it

aws:carestack:...

either, different error. Womp womp.)

stocky-spoon-28903

09/03/2018, 7:44 PM

@boundless-monkey-50243 you can look at https://GitHub.com/jen20/pulumi-aws-vpc too

stocky-spoon-28903

09/03/2018, 7:45 PM

That has most of the patterns you need for resource composition

rough-oil-1458

09/03/2018, 8:42 PM

@stocky-spoon-28903 thanks for that

boundless-monkey-50243

09/03/2018, 9:08 PM

@stocky-spoon-28903 will take a look, thanks.

boundless-monkey-50243

09/03/2018, 9:11 PM

Looks like I managed to wedge my stack in a way I've never done with TF. An RDS node got into an state such that when I deleted the RDS node, it has unrecoverably wedged (I did not specify a final snapshot identifier but apparently it defaulted to saving a final identifier - that seems...odd)

boundless-monkey-50243

09/03/2018, 9:12 PM

I manually deleted the RDS node, and the DNS entries that depended on it, but the state won't refresh

boundless-monkey-50243

09/03/2018, 9:13 PM

I can blow the whole thing away (now), but the discoverability of old states in my snapshot directory is a bit poor

boundless-monkey-50243

09/03/2018, 9:13 PM

error: /keybase/team/carestack.infra/pulumi/stacks/infra.json: snapshot integrity failure; refusing to use it: resource urn:pulumi:infra::infra::aws:ec2/instance:Instance::gitlab-app's dependency urn:pulumi:infra::infra::aws:rds/instance:Instance$aws:route53/record:Record::gitlab-db-dns comes after it

boundless-monkey-50243

09/03/2018, 9:19 PM

Unsure how it wedged, but I was able to manually pull remove those resources/references from my stack JSON and resurrect it.

fresh-king-3299

09/04/2018, 4:02 AM

I’m trying to work on the pulumi-kubernetes plugin and am able to build it. How can I update my pulumi installations to use my changes?

creamy-potato-29402

09/04/2018, 4:03 AM

make build && make install

ought to do the trick.

creamy-potato-29402

09/04/2018, 4:03 AM

make sure you’re picking up the updated version of

pulumi-resource-kubernetes

, though!

creamy-potato-29402

09/04/2018, 4:04 AM

run

where pulumi-resource-kubernetes

to see what’s on your path.

fresh-king-3299

09/04/2018, 4:04 AM

It looks like it’s in my home

find ~ -name pulumi*
/root/.pulumi/plugins/resource-kubernetes-v0.16.0/pulumi-resource-kubernetes
/root/.pulumi/bin/pulumi-language-nodejs
/root/.pulumi/bin/pulumi-language-python
/root/.pulumi/bin/pulumi-resource-pulumi-nodejs
/root/.pulumi/bin/pulumi-language-go
/root/.pulumi/bin/pulumi-language-python-exec
/root/.pulumi/bin/pulumi

creamy-potato-29402

09/04/2018, 4:04 AM

you may also want an updated pulumi/pulumi

creamy-potato-29402

09/04/2018, 4:05 AM

I get something like:

$ where pulumi-resource-kubernetes
/Users/alex/.pulumi/bin/pulumi-resource-kubernetes