The docs (https://www.pulumi.com/docs/reference/pkg/nodejs/pulumi/gcp/dns/#RecordSet) show this code with

accessConfig.0.natIp

. Is this valid TS?

const frontendRecordSet = new gcp.dns.RecordSet("frontend", {
    managedZone: prod.name,
    rrdatas: [frontendInstance.networkInterfaces[0].accessConfig.0.natIp],
    ttl: 300,
    type: "A",
});

is there any reasonably simple way for me to test this: https://github.com/pulumi/pulumi-azure/pull/361 to see if it also fixes https://github.com/pulumi/pulumi-azure/issues/359

alright so after working with Pulumi programs for a while on my local, it’s time to put everything in my CI.. oh wait, yaml files.. I got so spoiled by not working with disgusting yaml files that writting my CI sequence in it feels weird and unefficient… any thoughts? I’d love to have CI/CD as code

can I execute cmd commands in a pulumi program? I would like to

git clone

a helm chart and run it after

is it possible to have a Pulumi.yaml in a parent folder and have the Pulumi.<stack-name>.yaml in sub directories? right now I just copy my Pulumi.yaml over

Any tips or best practices for Kubernetes namespaces vs Pulumi’s stacks? I’m reading the docs right now, not sure if I saw something about it

how is admin status in Pulumi orgs determined if we’re using Github integration

troubleshooting a new issue that cropped up in Azure VM land.. i’m pretty sure it’s an azure issue, but not even sure where to start

panic: fatal: An assertion has failed: Kubernetes GVK is: "urn:pulumi:gke01-london::gcp-gke::gcp:compute/securityPolicy:SecurityPolicy::ingress-stable-protected-iap-whitelist-trusted-ips"

, full stack trace inside

How can I see what change triggers a

replace

instead of an

update

for a resource? We’re having some `gcp.container.Cluster`s (GKE clusters) and I want consider if a change introducing a replace of the whole cluster is worth it or not. If so, every service running it would need to be redeployed (not so nice).

is it possible for pulumi to perform all deletions in the plan first? not per resource, but globally? also these are not replacements (from pulumi POV)

pulumi refresh

shows differences where there are no one. Here in the

nodeConfig

on updating

gcp:container/nodePool:NodePool

. Where relies this bug: Pulumi or Terraform provider? I.e., in which Github repo must I search for an issue?

I'd really benefit from

pulumi stack mv $oldURN $newURN

or even

pulumi stack reparent $fromParentURN $toParentURN

Is there any way to apply pulumi script directly from TS/Node.js instead of using the CLI ?

Config with

1.0

and

1.1

seems pretty broken due to change in the stack naming: https://github.com/pulumi/pulumi/issues/3223

I’m struggling with defining

dynamic.Resource

properties - how do I return info from the backing cloud object via the Resource object here?

const TestProvider = {
  async create(inputs) {
    // some api call result
    const derivedVal = "foobar";

    return {
      id: "id",
      outs: { inputVal: inputs.inputVal, derivedVal: derivedVal
      }
    };
  }
};

class TestResource extends pulumi.dynamic.Resource {
  constructor(name, props, opts) {
    super(TestProvider, name, props, opts);
  }
}

const testResource = new TestResource("test-token", {
  inputVal: "bar"
});

console.log(testResource.inputVal); // 'OutputImpl { ...'
console.log(testResource.derivedVal); // undefined

see this issue https://github.com/pulumi/pulumi/issues/2931

i think the docs are updated now too https://www.pulumi.com/docs/intro/concepts/programming-model/#dynamic-resource-outputs

I’m using the Azure provider with a

ServicePrincipal

authentication instead of the default CLI one. Now in one case the

ServicePrincipal

I used had too few permissions to create `RoleAssignment`s. I now observe some inconsistencies between the pulumi state and what was created in the Azure subscription. Pulumi thinks everything but the `RoleAssignment`s has been created. With the corresponding permissions added to the

ServicePrincipal

this now leads to the issue that the

RoleAssignment

cannot be created as the desired

ServicePrincipal

(not the login one) I want to assign the role doesn’t exist. This looks like a bug to me because Pulumi should not store resources (e.g. the

ServicePrincipal

I wanted to create) if this was not successfully persisted at the provider level. Is there a way I can support debugging that case? I already did a

pulumi refresh

which showed some resources as

delete

but the case should be reproducible.

After doing a

pulumi up

with my

k8s.apps.v1.Deployment

, k8s (or Pulumi?) replaced all existing pods immediately instead of replacing in a one-by-one fashion, waiting for the readinessProbe to become true. Is this something I need to configure Pulumi to do?

GitHub Pulumi Action is failing for me with

pulumi:providers:gcp (default_1_0_0):
    error: no resource plugin 'gcp-v1.0.0' found in the workspace or on your $PATH, install the plugin using `pulumi plugin install resource gcp v1.0.0`
 
##[error]Docker run failed with exit code 255

From what I can tell, the Pulumi action doesn't

plugin install

prior to the

pulumi

command.

pulumi

cli doesn't respect

HOME=

, so it always installs plugins to

getent

home, which isn't persisted by GitHub Actions

i'd like to add some unit tests to my code. i'd like to test multiple properties on multiple objects. is there a way to do that with mocha/jest without having to wrap it all in a promise like

return new Promise((resolve, reject) => {
  let num = 0;
  object1.apply(o => {
    expect(o.prop1).toBe(something);
    expect(o.prop2).toBe(somethingElse);
    num++;
    if (num === 2) {
      done();
    }
  });
  object2.apply(o => {
    expect(o.prop1).toBe(something);
    expect(o.prop2).toBe(somethingElse);
    num++;
    if (num === 2) {
      done();
    }
  });
});

i know in QUnit you can do

const done = QUnit.done(2);
object1.apply(o => {
  expect(o.prop1).toBe(something);
  expect(o.prop2).toBe(somethingElse);
  done();
});
object2.apply(o => {
  expect(o.prop1).toBe(something);
  expect(o.prop2).toBe(somethingElse);
  done();
});

so i might just end up switching to that, but i'm wondering how you all run these kinds of tests with not-QUnit

Hey folks - I'm going to be starting my first project on Pulumi in the next week or so. As I'm preparing myself and doing research, I have two questions that I haven't found satisfactory answers to. Wondering if folks in this community have good feedback: 1. How do your orchestrate database migrations? Do you just use an out-of-the-box library for regular apps, and kick it off in a lambda during each push? Or does Pulumi have a suggested way of doing this? 2. How do you develop locally? My reading indicates the answer is just "test driven development"... but I'm not sure that's always reasonable. One of my lambdas, for instance, will generate a PDF. It's gonna be way easier to develop that if I can actually generate a PDF and look at it, rather than trying to unit test PDF outputs.

I'm new to serverless architectures, so forgive me if these are already obviously solved problems.

Can anyone explain why --stack flag doesn't work on

pulumi stack ls

command?

Hi, getting a panic when trying to destroy stack:

pulumi:pulumi:Stack  pubsub-service-pubsub-staging-shared           debug: Setting AWS metadata API timeout to 100ms

panic: fatal: An assertion has failed

goroutine 187 [running]:
<http://github.com/pulumi/pulumi/pkg/util/contract.failfast(...)|github.com/pulumi/pulumi/pkg/util/contract.failfast(...)>
        /private/tmp/pulumi-20190913-17277-15zhmar/src/github.com/pulumi/pulumi/pkg/util/contract/failfast.go:23
<http://github.com/pulumi/pulumi/pkg/util/contract.Assert(...)|github.com/pulumi/pulumi/pkg/util/contract.Assert(...)>
        /private/tmp/pulumi-20190913-17277-15zhmar/src/github.com/pulumi/pulumi/pkg/util/contract/assert.go:26
<http://github.com/pulumi/pulumi/pkg/resource/deploy.NewDeleteStep(0xc0010d0f00|github.com/pulumi/pulumi/pkg/resource/deploy.NewDeleteStep(0xc0010d0f00>, 0xc001234d00, 0xc001128850, 0x68)
        /private/tmp/pulumi-20190913-17277-15zhmar/src/github.com/pulumi/pulumi/pkg/resource/deploy/step.go:238 +0x261
<http://github.com/pulumi/pulumi/pkg/resource/deploy.(*stepGenerator).GenerateDeletes(0xc0005e25a0|github.com/pulumi/pulumi/pkg/resource/deploy.(*stepGenerator).GenerateDeletes(0xc0005e25a0>, 0xc0014bfc00, 0x2, 0x0)
        /private/tmp/pulumi-20190913-17277-15zhmar/src/github.com/pulumi/pulumi/pkg/resource/deploy/step_generator.go:551 +0x77d
<http://github.com/pulumi/pulumi/pkg/resource/deploy.(*planExecutor).Execute.func3(0xc0015d98c0|github.com/pulumi/pulumi/pkg/resource/deploy.(*planExecutor).Execute.func3(0xc0015d98c0>, 0xc000239be0, 0xc0006e58f0, 0x24c7aa0, 0xc0010c3f40, 0x24c7aa0, 0xc0010c3f00, 0x10000, 0x1, 0xc000761400)
        /private/tmp/pulumi-20190913-17277-15zhmar/src/github.com/pulumi/pulumi/pkg/resource/deploy/plan_executor.go:155 +0x3d5
<http://github.com/pulumi/pulumi/pkg/resource/deploy.(*planExecutor).Execute(0xc000239be0|github.com/pulumi/pulumi/pkg/resource/deploy.(*planExecutor).Execute(0xc000239be0>, 0x24c7aa0, 0xc0010c3f00, 0x24c7ea0, 0xc000af8000, 0x7fffffff, 0x10000, 0x1, 0x0, 0x0)
        /private/tmp/pulumi-20190913-17277-15zhmar/src/github.com/pulumi/pulumi/pkg/resource/deploy/plan_executor.go:192 +0x511
<http://github.com/pulumi/pulumi/pkg/resource/deploy.(*Plan).Execute(...)|github.com/pulumi/pulumi/pkg/resource/deploy.(*Plan).Execute(...)>
        /private/tmp/pulumi-20190913-17277-15zhmar/src/github.com/pulumi/pulumi/pkg/resource/deploy/plan.go:330
<http://github.com/pulumi/pulumi/pkg/engine.(*planResult).Walk.func1(0x24c7ea0|github.com/pulumi/pulumi/pkg/engine.(*planResult).Walk.func1(0x24c7ea0>, 0xc000af8000, 0xc001568160, 0x24c7aa0, 0xc0010c3f00, 0x20e5401, 0xc0006e58e0, 0xc0015d96e0)
        /private/tmp/pulumi-20190913-17277-15zhmar/src/github.com/pulumi/pulumi/pkg/engine/plan.go:182 +0x13b
created by <http://github.com/pulumi/pulumi/pkg/engine.(*planResult).Walk|github.com/pulumi/pulumi/pkg/engine.(*planResult).Walk>
        /private/tmp/pulumi-20190913-17277-15zhmar/src/github.com/pulumi/pulumi/pkg/engine/plan.go:173 +0x11b

Is that a known issue?

Since the v1.1.0 upgrade

pulumi up

always detects a change in an EBS volume attachment though nothing changed:

$ pulumi up
Previewing update (acmecorp-demo):

     Type                                                 Name                           Plan        Info
     pulumi:pulumi:Stack                                  private-cloud-acmecorp-demo              
 +-  ├─ aws:ec2:Instance                                  services                       replace     [diff: ~ebsBlockDevices]
     ...

Resources:
    +-8 to replace
    156 unchanged

Do you want to perform this update? details
  pulumi:pulumi:Stack: (same)
    [urn=urn:pulumi:acmecorp-demo::private-cloud::pulumi:pulumi:Stack::private-cloud-acmecorp-demo]
    ++aws:ec2/instance:Instance: (create-replacement)
        [id=i-0eba90d7bd7c11af4]
        [urn=urn:pulumi:acmecorp-demo::private-cloud::aws:ec2/instance:Instance::services]
        [provider=urn:pulumi:acmecorp-demo::private-cloud::pulumi:providers:aws::default_0_18_27::4e650a8e-8d3d-4c3c-a9d1-b31c8638bd95]
      ~ ebsBlockDevices: [
          ~ [0]: {
                  ~ deleteOnTermination: true => true
                  ~ deviceName         : "/dev/sdf" => "/dev/sdf"
                  + encrypted          : true
                  + volumeSize         : 100
                  + volumeType         : "gp2"
                }
        ]
    +-aws:ec2/instance:Instance: (replace)
        [id=i-0eba90d7bd7c11af4]
        [urn=urn:pulumi:acmecorp-demo::private-cloud::aws:ec2/instance:Instance::services]
        [provider=urn:pulumi:acmecorp-demo::private-cloud::pulumi:providers:aws::default_0_18_27::4e650a8e-8d3d-4c3c-a9d1-b31c8638bd95]
      ~ ebsBlockDevices: [
          ~ [0]: {
                  ~ deleteOnTermination: true => true
                  ~ deviceName         : "/dev/sdf" => "/dev/sdf"
                  + encrypted          : true
                  + volumeSize         : 100
                  + volumeType         : "gp2"
                }
        ]

has anyone experienced just complete hangs on pulumi commands no matter what the command?