Hi, I’m trying to build a bootstrap program that will provision multiple organization accounts, each with its own VPC and EKS. The problem however is that https://github.com/pulumi/pulumi-awsx/blob/master/nodejs/awsx/ec2/vpc.ts#L25 does not support custom providers. For example, https://github.com/pulumi/pulumi-awsx/blob/master/nodejs/awsx/ec2/vpc.ts#L68 creates a VPC, not forwarding the provided custom providers. On the other hand, there’s https://github.com/pulumi/pulumi-awsx/blob/master/nodejs/awsx/ec2/vpcTopology.ts#L28 which does forward the provided opts to the created resource (https://github.com/pulumi/pulumi-awsx/blob/master/nodejs/awsx/ec2/vpcTopology.ts#L121), but it seems there’s a problem. ComponentResourceOptions defines a map of providers:

export interface ComponentResourceOptions extends ResourceOptions {
    providers?: Record<string, ProviderResource>;
}

However, the Subnet is a

Resource

, not a

Component

and thus expects:

export interface CustomResourceOptions extends ResourceOptions {
    provider?: ProviderResource;
}

Which has only a single provider. I created a PR https://github.com/pulumi/pulumi-awsx/pull/176, but I see it doesn’t advance. Please suggest how to achieve custom providers support across all pulumi modules

If pulumi is changing the names of all the services, how is everyone referencing these services? Do you have a separate service directory mechanism?

Hi -- exploring Pulumi. I really like the design. I'm trying to figure out if I can use it to support my development workflow for a personal project. I need to spin up gpu instances in the cloud for running code in anaconda environments with gpu support. I've been manually setting up machines and rsync'ing data (its feasible to rsync data for my problem size) to them to support development. I'm wanting to see if I can build an abstraction on top of (or composing) aws.ec2.Instance to manage a portion of the filesystem on the instance(s) via (something like) rsync. Is the right thing to just use pulumi to manage the lifecycle of the instance(s) and then interrogate pulumi with

pulumi stack output --json

from another script to figure out how to contact the hosts and drive the rsyncing there? Doers that sound like a possible approach or other recommendations on how to do this? If I'm using pulumi typescript can I get the equivalent of

pulumi stack output --json

somehow without manually invoking the pulumi command and parsing the json output myself -- ideally in a way that preserves type info and auto-complete behavior

Hi, I’m working on support for

assumeRole

in EKS (https://github.com/pulumi/pulumi/issues/2537). For this I want to parse the aws provider at https://github.com/pulumi/pulumi/issues/2537. Is there a way I can get a reference to the aws provider in use?

has anyone outside of the pulumi team created a tf provider?

@calm-greece-42329 Yes! A couple of people have, it’s not as simple as it should be right now because I’m in the process of updating the boilerplate to use Go Modules instead of dep. That does make things dramatically simpler though.

that was kind of the headache i ran into 😛

I can give you the tl;dr on how to do it if you want:

the template also used a variable for the

<http://github.com/pulumi/<repo>|github.com/pulumi/<repo>>

in some places, but not all places, so i wasnt sure if there was a reason for that (like installing the provider as a user later) or if the repo should plan on landing in the pulumi space for ease of use

sure

(Ultimately they probably want to land in the

pulumi

namespace for now, until we sort out the ability for third party packages to install via

pulumi plugin install

)

ok, i’ll plan on that

fwiw its for https://github.com/sky-uk/terraform-provider-infoblox which is probably going to be something somewhat common

From the current boilerplate repo: 0. Clone into the target path inside GOPATH even though we are using modules 1. Remove

Gopkg.*

2. Temporarily

export GO111MODULE=on

3.

go get <http://github.com/pulumi/pulumi-terraform@master|github.com/pulumi/pulumi-terraform@master>

4.

go get <http://github.com/terraform-providers/terraform-provider-xyz@releasetag|github.com/terraform-providers/terraform-provider-xyz@releasetag>

5. go mod vendor 6.

unset GO111MODULE

7. In .travis.yml, bump to

go: 1.12.1

(but not further) 8. Apply the diff to

build/common.mk

from here: https://github.com/pulumi/pulumi-aws/pull/514/files#diff-fd68401511ad5f7f12fb687d58ec8076 9.

go get <http://github.com/pulumi/scripts/gomod-doccopy|github.com/pulumi/scripts/gomod-doccopy>

9. The rest should be the same as the instructions

Actually step 4a: copy the

replace

block from here into `go.mod`:https://github.com/pulumi/pulumi-aws/pull/514/files#diff-37aff102a57d3d7b797f152915a6dc16R30 and line 31

not happy, ill wipe my mods and try again

@calm-greece-42329 That’s step 4a 🙂

😄

It’s pretty irritating that replacements can’t be done at the library level, but that’s unfortunately how it is right now 😞

ok finished step 9. ill chug along in the normal docs but no problems with that 👍

is there a way to make a configuration option non-optional? 🙂

for example the TF param is required:

// "password": &schema.Schema{
			// 	Type:        schema.TypeString,
			// 	Required:    true,
			// 	DefaultFunc: schema.EnvDefaultFunc("INFOBLOX_PASSWORD", nil),
			// 	Description: "Password to authenticate with Infoblox appliance",
			// },

or being able to cast them as bool, or ints, stuff like that

Yes, if there is no Default and it’s Required

🎉 https://github.com/bigkraig/pulumi-infoblox

hmm if i push it to npm will i be able to use it?

i guess its kind of set up to go to the pulumi s3 hmm

Hi, I want to run ansible-playbook using Pulumi (like Terraform with local-exec module or remote-exec) there is any provisioner like that in Pulumi i can use ? 10x 🙂

@calm-greece-42329 You’ll be able to use it, but not install the plugin as part of the post-install script

Hi all