I have to say that sometimes getting to a pulumi output value and passing it to other things can be maddening. I am retrieving all of the usernames from an AWS IAM group to use in other places.

const iamGroup = pulumi.output(aws.iam.getGroup({
    groupName: "myGroup",
}, { async: true }));

const usernames = iamGroup.apply(group => group.users.map(user => user.userName));

If I

export

const usernames, I see

Outputs:
    usernames: [
        [0]: "username1"
        [1]: "username2"
        [2]: "username3"
    ]

However, later when attempting to use both

.filter

and

.map

on the

usernames

list, I get

TSError: ⨯ Unable to compile TypeScript:
    index.ts(312,13): error TS2488: Type 'Output<string[]>' must have a '[Symbol.iterator]()' method that returns an iterator.
    index.ts(469,42): error TS2339: Property 'map' does not exist on type 'Output<string[]>'.

I have tried many variations of

.apply

but am so far unable to use the above methods or return this list from the function it is in. I have read the Inputs and Outputs doc many times but it is still painful to figure out how to make it work.

I’ve created a reusable Nodejs package

aws-resource

for creating AWS resources. The package

aws-resource

is used inside a Pulumi stack. When I execute the unit tests of the Pulumi stack, it complains with ‘_Error: Program run without the Pulumi engine available; re-run using the

pulumi

CLI_’. Although the unit tests of the stack contain the mocking code for Pulumi resources.

pulumi.runtime.setMocks({
  newResource: function(...) { ... }
});

I guess the pulumi API calls inside the Nodejs package

aws-resource

don’t get mocked. What should I do to also have the resources created by the package

aws-resource

mocked?

What's the prefered method of running typescript in node nowadays? and is there any difference? Docs state ts-node and tsc variants - any thoughts?

...and what does pulumi use internally? 😉

Is there a way to use

pulumi import

without updating state possibly?

Has anyone got a functional launch.json or similar, to get debugging working with Pulumi?

Hi! I have a Typescript newbie question about Pulumi outputs and promises. I would expect the following to work but I'm getting a type error:

const promise = new Promise<Map<string, string>>((resolve, reject) => new Map<string, string>());
const output: pulumi.Output<Map<string, string>> = pulumi.output(promise);

as it fails with:

TS2322: Type 'Output<UnwrappedObject<Map<string, string>>>' is not assignable to type 'Output<Map<string, string>>'.   Type 'Output<UnwrappedObject<Map<string, string>>>' is not assignable to type 'OutputInstance<Map<string, string>>'.     Types of property 'apply' are incompatible.       Type '{ <U>(func: (t: UnwrappedObject<Map<string, string>>) => Promise<U>): Output<U>; <U>(func: (t: UnwrappedObject<Map<string, string>>) => OutputInstance<...>): Output<...>; <U>(func: (t: UnwrappedObject<...>) => U): Output<...>; }' is not assignable to type '{ <U>(func: (t: Map<string, string>) => Promise<U>): Output<U>; <U>(func: (t: Map<string, string>) => OutputInstance<U>): Output<U>; <U>(func: (t: Map<...>) => U): Output<...>; }'.         Types of parameters 'func' and 'func' are incompatible.           Types of parameters 't' and 't' are incompatible.             Type 'UnwrappedObject<Map<string, string>>' is missing the following properties from type 'Map<string, string>': [Symbol.iterator], [Symbol.toStringTag]

Am I missing something? I thought that I can "repackage" whatever I have in the promise object into an output object.

Hi! I'm using aws sdk for secrets manager and I'm getting issue like this: https://github.com/aws/aws-sdk-js-v3/issues/1919

Is there any way to use TypeScript 4.x with Pulumi?

I noticed typescript aws.ec2.wafv2 has no examples, which I think means that it's not gotten a lot of qa and love. Other than that, should I expect it to work? it is not a hot button issue in the issues tracker

is:issue waf is:closed

is 1 issue.

Hi Everyone😃 Our stack is currently written with TypeScript (TS) and have implemented Airflow in AWS. Now, we need to dynamically reference TS resources in Python and have no idea how to do that in manageable way (without just hard-coding them). Is there a way to do this?

Made a small PR against one of the example repositories to help with an issue presented here: https://pulumi-community.slack.com/archives/C84L4E3N1/p1618199806445700

Dear typescript, please let me be lazy I dont wanna type the full word boolean instead of the short form bool. Please stop making me a better dev I dont wanna.

Does anyone know how I can extract subnetId from my network I am instantiating? There is a resource Azure AD Domain Services which requires a subnetId to be passed to it. https://www.pulumi.com/docs/reference/pkg/azure-native/aad/domainservice/

Hello! I'm new to Pulumi and trying to follow this tutorial for a JS setup. Is this the right spot to ask some questions? https://www.pulumi.com/docs/guides/testing/integration/

Alright, I tried. I dont seem to understand how to output this subnetsId. If someone can help point me in the right direction, I would greatly appreciate it. here is my code so far.

What's the best way to decrypt pulumi secret?

does pulumi offer any functions to generate kubeconfig's ? I have an existing kubernetes cluster, and I want to try and connect to it using pulumi + typescript, the provider can accept a kubeconfig (https://www.pulumi.com/docs/reference/pkg/kubernetes/provider/) which is easy if i'd created the cluster using

pulumi-eks

. what am I missing?

So I have some Subnets built and a SecurityGroup. I dont see anywhere in the docs for NSG stating how you go about attaching this to a subnet. Here is my code so far

const USNetWork = new azure_native.network.VirtualNetwork(usNetName, {
    resourceGroupName: RG,
    location: "WestUS",
    virtualNetworkName: usNetName,
    addressSpace: {
        addressPrefixes: [usAddr],
    },

});

const domainSubnetUSA = new azure_native.network.Subnet(usADDSSubnetName, {
    resourceGroupName: RG,
    subnetName: usADDSSubnetName,
    virtualNetworkName: USNetWork.name,
    addressPrefix: usADDSSubnetaddr,
  });

  const meshSubnetUSA = new azure_native.network.Subnet(usMESHSubnetName, {
    resourceGroupName: RG,
    subnetName: usMESHSubnetName,
    virtualNetworkName: USNetWork.name,
    addressPrefix: usMESHSubnetaddr,
  });

  const InboundSGUSA = new azure_native.network.NetworkSecurityGroup("InboundSG", {
    location: "WestUS",
    networkSecurityGroupName: "Test",
    resourceGroupName: RG,
    securityRules: [allowPSRM,allowRDP],
});

OutputInstance

defines these:

apply<U>(func: (t: T) => Promise<U>): Output<U>;
    apply<U>(func: (t: T) => OutputInstance<U>): Output<U>;
    apply<U>(func: (t: T) => U): Output<U>;

Shouldn't they be?

apply<U>(func: (t: T) => Promise<U> | OutputInstance<U> | U): Output<U>;

Otherwise if

func

is something like

string => number | Promise<number>

then it returns

Output<number | Promise<number>>

rather than

Output<number>

. Unless that was intentional?

Is there any update on pulumi supporting yarn 2?

I was also curious, why are there so many variations for types? I seems to really slow down vscode.

After upgrading to pulumi v3.0.0 and upgrading all my pulumi npm packages, I am seeing this. I've never had to install a plugin manually before. Anyone know why I'm getting this?

$ pulumi up
Previewing update (eks-dev):
[resource plugin kubernetes-2.8.2] installing
Downloading plugin: 0 B / 28.83 MiB [----------------------------------]   0.00%[resource plugin aws-3.31.0] installing
Downloading plugin: 28.83 MiB / 28.83 MiB [=========================] 100.00% 2s
Downloading plugin: 74.84 MiB / 74.84 MiB [=========================] 100.00% 4s
     Type                     Name                    Plan     Info
     pulumi:pulumi:Stack      infrastructure-eks-dev           
     └─ pulumi:providers:eks  default                          1 error
 
Diagnostics:
  pulumi:providers:eks (default):
    error: no resource plugin 'eks' found in the workspace or on your $PATH

Hey Guys! If I’m using TypeScript with Pulumi, what is the latest 

target

 I can use? Currently the default seems to be 

es2016

. Is there any reason why won’t I bump it to 

es2020

? Also, as for the 

module

 definition, can I use 

ES2020

 or 

ESNext

?

What are the best practices for TS Pulumi app structure?

Has anyone written unit tests that include the bundling of async code for things like Lambdas? I'm trying to find a way around https://github.com/pulumi/pulumi/issues/5832 but I'm continually hitting

unhandled rejection: CONTEXT(3262): transferDeps( ...

Why can’t we use

target: "es2020"

in our

tsconfig.json

file? Why are we locked to

es2016

?