So when’s the first PulumiCon!?

I think a 1.0 launch deserves it 🙂

dang,

getResourceProperty

results in errors 😞

I’ve read, and employed, the instructions for unit testing from the recent blog post. That is not a sufficient solution. Especially so when developing custom components and functions. A mock runtime would be a step in the right direction. Requiring us to build a stack when none is needed just to test reusable components is not the answer.

trying to get a secret from

aws.secretsmanager

but the documentation has me confused on how I actually pass the secret into my resource. Anybody have an example?

Hello what permissions in RBAC do I need to create watchers for ReplicaSet’s in pulumi. I am using EKS and I see this error

Could not create watcher for ReplicaSet objects associated with Deployment

Say I have a resource B, that depends on resource A via one of its outputs. Is there any straightforward way to force B to update any time A updates, even if the change in A is not one of the outputs that B depends on?

@bitter-island-28909 I believe you can use

dependsOn

for that

will pulumi reorder resources when importing yaml? i.e. can i simply slurp up https://github.com/jetstack/cert-manager/releases/download/v0.9.1/cert-manager.yaml or will that break?

i get a bunch of failed creations when i try just importing the yaml 😞

I moved all of our resources to other modules imported by index.ts and pulumi wants to delete everything 😬 — what am I missing?

looking for any examples or pointers on how to get a Resource for an existing dynamodb table and then use that in a role+policy pair for a lambda. getting held up on if

aws.dynamodb.getTable({name: 'mytablename'})

is what i need to get the resource. tried wrapping in an async function but it seems to just not build the resource at all.

Is there any way to always have a resource imported if it doesn’t exist? The scenario is that we have the GKE Istio addon enabled. We want to be able to change the HPA minReplicas to 2 (from 1). In order to be able to do this, we have to have the resource in pulumi. The only way I know of being able to do this is to import the resource. However, let’s say we create a new stack, then obviously the resource won’t be created by Pulumi but by GKE. Thus the resource will be attempted to be created by pulumi as well as it doesn’t know to import the created resource created by GKE.

Anybody got some more resources on how to get started writing a custom provider? I find the kubernetes one a bit daunting to get started

Any reason why the example from the typescript ec2.SecurityGroup source fails to typecheck?

const allowTls = new aws.ec2.SecurityGroup('allowTls', {
  description: 'Allow TLS inbound traffic',
  ingress: [
    {
      cidrBlocks: '', 
      fromPort: 443,
      protocol: 'tcp',
      toPort: 443
    }
  ],
  tags: {
    Name: 'allowAll'
  }
});

I'm getting a long cryptic typescript error that isn't much use in indicating what is actually wrong.

Error:(12, 56) TS2345: Argument of type '{ description: string; ingress: { cidrBlocks: string; fromPort: number; protocol: string; toPort: number; }[]; tags: { Name: string; }; }' is not assignable to parameter of type 'SecurityGroupArgs'.
  Types of property 'ingress' are incompatible.
    Type '{ cidrBlocks: string; fromPort: number; protocol: string; toPort: number; }[]' is not assignable to type 'Input<{ cidrBlocks?: Input<string>[] | Promise<Input<string>[]> | OutputInstance<Input<string>[]> | undefined; description?: string | Promise<string> | OutputInstance<string> | undefined; ... 6 more ...; toPort: Input<...>; }>[] | Promise<...> | OutputInstance<...> | undefined'.
      Type '{ cidrBlocks: string; fromPort: number; protocol: string; toPort: number; }[]' is not assignable to type 'Input<{ cidrBlocks?: Input<string>[] | Promise<Input<string>[]> | OutputInstance<Input<string>[]> | undefined; description?: string | Promise<string> | OutputInstance<string> | undefined; ... 6 more ...; toPort: Input<...>; }>[]'.
        Type '{ cidrBlocks: string; fromPort: number; protocol: string; toPort: number; }' is not assignable to type 'Input<{ cidrBlocks?: Input<string>[] | Promise<Input<string>[]> | OutputInstance<Input<string>[]> | undefined; description?: string | Promise<string> | OutputInstance<string> | undefined; ... 6 more ...; toPort: Input<...>; }>'.
          Type '{ cidrBlocks: string; fromPort: number; protocol: string; toPort: number; }' is not assignable to type '{ cidrBlocks?: Input<string>[] | Promise<Input<string>[]> | OutputInstance<Input<string>[]> | undefined; description?: string | Promise<string> | OutputInstance<string> | undefined; ... 6 more ...; toPort: Input<...>; }'.
            Types of property 'cidrBlocks' are incompatible.
              Type 'string' is not assignable to type 'Input<string>[] | Promise<Input<string>[]> | OutputInstance<Input<string>[]> | undefined'.

Running v0.17.28. Thanks

What is analyzers/Policy?

Started getting this since this morning:

Found incompatible versions of @pulumi/pulumi.  Differing major or minor versions are not supported.
      Version 0.17.28 referenced at node_modules\@pulumi\kubernetes\node_modules\@pulumi\pulumi\package.json
      Version 1.0.0-beta.2 referenced at node_modules\@pulumi\pulumi\package.json

Is this known / expected?

Our org was renamed per our requests, but now stacks don't work:

Previewing update ($NEWORG/prod):
error: could not deserialize deployment: decrypting secret value: [404] Not Found: Organization '$OLDORG' not found

What do I miss?

pulumi.output(new gcp.compute.Subnetwork("z", {ipCidrRange: "111", network: "zzz"})).name;

Error on `tsc --noEmit`:

Property 'name' does not exist on type 'OutputInstance<Subnetwork>'.

16 pulumi.output(new gcp.compute.Subnetwork("z", {ipCidrRange: "111", network: "zzz"})).name;

ok one more import related:

const dbUser = new gcp.sql.User("myuser", {
    instance: dbInstance.name,
    name: "project/instancename/myuser"
}, { import: "project/instancename/myuser" })

ends up in

Preview failed: reading resource urn:pulumi:projectname::stackname::gcp:sql/user:User::project/instancename/myuser yielded an unexpected ID; expected project/instancename/myuser, got myuser//instancename

anyone faced this before?

aws.acm.CertificateValidation deletes the cert after it is issued

I created a new stack for a new project, without using

pulumi new

but now the project name is not showing up on the dashboard. I made sure that the project name in Pulumi.yaml was set correct, any reason why

stack init

wouldn't name these correctly?

Hello - new to Pulumi. Trying to Build a new IAM Policy Statement using the IP Address conditions. Pulumi doesn’t want to assign the array to the ConditionArguments.

Is there a straightforward way to transplant an existing resource to a new provider?

@microscopic-florist-22719 Do you guys plan to have your own tap since https://github.com/Homebrew/homebrew-core/pull/43113 seems like it’s going to be a while before it’s resolved, if they even let you guys stay?

Just started getting this error randomly: error: could not read plugin [/home/vagrant/.pulumi/plugins/resource-kubernetes-v0.24.0/pulumi-resource-kubernetes] stdout: EOF

Has anyone come across this?

Any ideas why though the input for

parameters

says

[key: string]: any;

it won’t take a dictionary? Error:

parameters ($connections): '' expected type 'string', got unconvertible type 'map[string]interface {}'

const processWorkflow = new azure.logicapps.Workflow('process-url', {
    location: resourceGroup.location,
    resourceGroupName: resourceGroup.name,
    parameters: {
        "$connections": {
            "defaultValue": {},
            "type": "Object"
        }
    }
});

Alternatively, I’m trying this too, to try and establish the connection between CosmosDB and a LogicApp (the API Connector is already created) in the following way:

const processWorkflow = new azure.logicapps.Workflow('process-url', {
    location: resourceGroup.location,
    resourceGroupName: resourceGroup.name,
    parameters: {
        "$connections": JSON.stringify({
            // "defaultValue": {},
            // "type": "Object"
            "value": {
                "documentdb": {
                    "connectionId": "/subscriptions/639952d4-dcc0-49f4-a588-d59bfb63cf4b/resourceGroups/shortener-rg0620430b/providers/Microsoft.Web/connections/api-connection-to-cosmosdb",
                    "connectionName": "logicapp-comosdb-connection",
                    "id": "/subscriptions/639952d4-dcc0-49f4-a588-d59bfb63cf4b/providers/Microsoft.Web/locations/westeurope/managedApis/documentdb"
                }
            }
        })
    }
});