Is there a way to log to the correct resource from a dynamic provider (js)? I'm able to do so from a component resource, but can't see an obvious way for resources backed by dynamic providers.

Is it normal that for every change I make to my infra, any docker images are uploaded each time - even if the changes are unrelated to that docker image?

is there a simpler way to rewrite this bit of typescript please?

Hi, nice work guys! Quick question, I can't find a command to figure out where I'm logged. I'm missing something?

I'm trying to create a Cosmos DB account with 5 regions and it invariably fails as described in https://github.com/pulumi/pulumi-azure/issues/219. Any hints or workarounds?

qq for the room, does anyone have any TypeScript code that shows how ignoreChanges is used as part of a provider?

@lemon-spoon-91807 hey man thanks for jumping into that #2455 cloud object store PR. do you know if there is anything tracking support for distributed locks? it was mentioned at the beginning of it but was dropped as a requirement

Anyone know if it is possible to use Service Principal certificates to access azure from the Pulumi config settings instead of just ClientSecret? Terraform uses

ARM_CLIENT_CERTIFICATE_PASSWORD

and

ARM_CLIENT_CERTIFICATE_PATH

, wondering if Pulumi has an equivalent. Couldn't find any docs.

are there any examples of cloudstorage or firebase besides the slack one in the examples folder? https://pulumi.io/reference as far as I can tell is empty on this.

Is there a way to log to the correct resource from a dynamic provider (js)? I'm able to do so from a component resource, but can't see an obvious way for resources backed by dynamic providers.

Is there a way to get the dns name for an

awsx.elasticloadbalancingv2.ApplicationLoadBalancer

?

I know you can get a listener endpoint

I guess any listener on an alb will have the same endpoint

Oh,

ApplicationLoadBalancer .loadBalancer.dnsName

Another question: is there a way to assign multiple target groups to a awsx FargateService? I get an error about multiple `load_balancer`s being set

I seem to always hit this error:

aws:ec2:SecurityGroupRule (fib-lb-listener-external-0-ingress):
    error: Plan apply failed: [WARN] A duplicate Security Group rule was found on (sg-0eb9f6d1b7d9a192b). This may be
    a side effect of a now-fixed Terraform issue causing two security groups with
    identical attributes but different source_security_group_ids to overwrite each
    other in the state. See <https://github.com/hashicorp/terraform/pull/2376> for more
    information and instructions for recovery. Error message: the specified rule "peer: 0.0.0.0/0, TCP, from port: 80, to port: 80, ALLOW" already exists

I'm using pulumi 0.17.8, awsx 0.18.3. It seems like it has something to do with

external: true

passed to

createListener

and explicitly passing a security group to

awsx.elasticloadbalancingv2.ApplicationLoadBalancer

.

Also just started receiving this message after running `pulumi up`:

TypeError: Converting circular structure to JSON
        at stringify (<anonymous>)
        at OutputImpl.<anonymous> (/home/kenny/compute_software/demo-applications/fibonacci/pulumi-fargate/node_modules/@pulumi/pulumi/output.js:102:47)
        at Generator.next (<anonymous>)
        at /home/kenny/compute_software/demo-applications/fibonacci/pulumi-fargate/node_modules/@pulumi/pulumi/output.js:20:71
        at new Promise (<anonymous>)
        at __awaiter (/home/kenny/compute_software/demo-applications/fibonacci/pulumi-fargate/node_modules/@pulumi/pulumi/output.js:16:12)
        at exports.Output.promise.then (/home/kenny/compute_software/demo-applications/fibonacci/pulumi-fargate/node_modules/@pulumi/pulumi/output.js:89:70)
        at <anonymous>

Could be related to just updating the CLI to 0.17.8.

Hi, I went ahead and opened the

hombrew

PR for 0.17.9 https://github.com/Homebrew/homebrew-core/pull/39443, but it fails on this new dep: https://github.com/pulumi/pulumi/blame/55b233fbdc4d59706f17d64e7618f28ddab6412d/go.mod#L43

Hi, I’m using the following script to get pulumi to show a preview of a PRs changes to a GKE cluster:

yarn --frozen-lockfile
pulumi stack select ...
pulumi refresh --yes
pulumi preview --diff

However, I get the following error when I run it in CI:

[2019-04-30T20:10:12Z] + pulumi refresh --yes
[2019-04-30T20:10:13Z] Previewing refresh (...):
[2019-04-30T20:10:14Z]
...
[2019-04-30T20:10:14Z]  ~  gcp:container:NodePool dogfood-full-k8s-node-pool refreshing error: Preview failed: refreshing urn:pulumi:ds-dog-k8s-dev::sg-deploy-k8s-helper::gcp:container/nodePool:NodePool::dogfood-full-k8s-node-pool: Error reading Container NodePool dogfood-full-k8s-node-pool: googleapi: Error 403: Request had insufficient authentication scopes., forbidden
[2019-04-30T20:10:14Z] ~ gcp:container:Cluster dogfood-full-k8s refreshing error: Preview failed: refreshing urn:pulumi:ds-dog-k8s-dev::sg-deploy-k8s-helper::gcp:container/cluster:Cluster::dogfood-full-k8s: Error reading Container Cluster "dogfood-full-k8s": googleapi: Error 403: Request had insufficient authentication scopes., forbidden

I gave the service account that pulumi uses the

Editor

and

Kubernetes Engine Developer

roles: https://cloud.google.com/kubernetes-engine/docs/how-to/iam Do you know if I need to give it any more permissions?

Hi! I’m kind of a Pulumi noob, and am testing it out in GCP. Running into this problem when running `pulumi up`:

$ pulumi up
Previewing update (dev):

     Type                 Name                      Plan       Info
 +   pulumi:pulumi:Stack  pulumi-test-function-dev  create     1 error

Diagnostics:
  pulumi:pulumi:Stack (incoming-measurement-dev):
    error: Running program '~/pulumi' failed with an unhandled exception:
    ~/pulumi/index.js:1
    (function (exports, require, module, __filename, __dirname) { import * as pulumi from "@pulumi/pulumi";
                                                                         ^

    SyntaxError: Unexpected token *
        at new Script (vm.js:80:7)
        at createScript (vm.js:274:10)
        at Object.runInThisContext (vm.js:326:10)
        at Module._compile (internal/modules/cjs/loader.js:664:28)
        at Object.Module._extensions..js (internal/modules/cjs/loader.js:712:10)
        at Module.load (internal/modules/cjs/loader.js:600:32)
        at tryModuleLoad (internal/modules/cjs/loader.js:539:12)
        at Function.Module._load (internal/modules/cjs/loader.js:531:3)
        at Module.require (internal/modules/cjs/loader.js:637:17)
        at require (internal/modules/cjs/helpers.js:22:18)

Here’s my stack code:

import * as pulumi from "@pulumi/pulumi";
import * as gcp from "@pulumi/gcp";


const bucket = new gcp.storage.Bucket("my-test-bucket", {});
const archive = new gcp.storage.BucketObject("archive", {
    bucket: bucket.name,
    source: new pulumi.asset.FileArchive("./artifacts/cloudfunction.zip"),
});

const functionFunction = new gcp.cloudfunctions.Function("function", {
    availableMemoryMb: 128,
    description: "pulumi-test-function",
    entryPoint: "hello_world",
    labels: {
        "cloudfunction": "pulumi-test-function",
    },
    sourceArchiveBucket: bucket.name,
    sourceArchiveObject: archive.name,
    timeout: 60,
    triggerHttp: true,
});

Glad you are up and running @rhythmic-australia-1932 ... feel free to let us know if you hit anything else.

Btw how did the Azure hackathon go?

Gave a 10 minute pulimi talk at work yesterday. Got some great responses, "there was so much yes in that presentation", "I'd actually learn Typescript for that".

Is there a way to reference existing resources, similar to what terraform's "data" does?

i've just updated to 0.17.9 and pulumi login file://blah doesnt work

it prompts for an access token

also, on 0.17.8:

An error occurred: unknown flag: --json
WARNING: Pulumi Preview failed.

yet it's in the changelog https://github.com/pulumi/pulumi/blob/master/CHANGELOG.md#0178-released-april-23-2019

pulumi RBAC - I just set it up so base access is READ by default and only our CI/CD account has WRITE

but it just let me modify a stack BUT it did not let my coworker