Are there any APIs that allow you to access and modify resources either by name, or by iterating through all resources? Use case: I’d like to add a “tag” to everything in a stack without having to go add it to the properties every single place I instantiate a resource. Is this kind of “metaprogramming” supported, in general? I can’t find it in the API docs but maybe I’m missing something.

Anyone have any tips on how to best develop event-driven serverless solutions on AWS using Pulumi, Github, and AWS Cloud9 & SAM for debugging & building compiled binaries?

This morning, we released support for webhooks in the Pulumi app. @colossal-beach-47527 has the details of how to hook up stack and team updates from Pulumi... with Pulumi. https://blog.pulumi.com/getting-to-chatops-with-pulumi-webhooks

This issue https://github.com/pulumi/pulumi-cloud/issues/627 is currently blocking me. I need to be able to set a Docker build arg from the output of another Pulumi resource. Is there a workaround for this?

I feel like failed resources should never stop a

pulumi refresh

from running. Is there an issue filed for that?

Good morning, I'm having trouble using pulumi with go + aws. I'm trying to create a security group and then use it's ID in another security group's Ingress rule but I keep getting an error like this:

error: aws:ec2/securityGroup:SecurityGroup resource 'sg1' has a problem: ingress.0: invalid or unknown key: source_security_group_id

Can anybody help me figure this one out?

Join us in 20 mins: https://twitter.com/PulumiCorp/status/1087764846865715200

Pulumi is live right now! 🎉 https://twitter.com/PulumiCorp/status/1087764846865715200

Hi All - Luke is taking questions right now!

you can either post your questions here or go to our youtube live stream chat, thanks!

After upgrading to the latest Pulumi on MacOs using brew, I get this version warning after running `pulumi up`:

warning: A new version of Pulumi is available. To upgrade from version '0.0.0' to '0.16.11', visit <https://pulumi.io/install> for manu
al instructions and release notes.

On AWS, in order to attach a scaling policy to a resource, you first need to register a scalable target. Is there a way on Pulumi to register a scalable target, as described here from Step 2 https://docs.aws.amazon.com/amazondynamodb/latest/developerguide/AutoScaling.CLI.html

The AWS API to register a scalable target https://docs.aws.amazon.com/autoscaling/application/APIReference/API_RegisterScalableTarget.html

Anyone can point me in the right direction as to how to debug a nodejs app called by pulumi in VS Code? 🤔

I keep getting these messages when creating a kubernetes ingress The ingress creates successfully and all of the services behind the path rules exist, so I’m not sure what’s going on.

~  kubernetes:extensions:Ingress internal-rpc updating error: No matching service found for ingress rule: ""
 ~  kubernetes:extensions:Ingress internal-rpc updating error: No matching service found for ingress rule: ""
 ~  kubernetes:extensions:Ingress internal-rpc updating error: No matching service found for ingress rule: ""
 ~  kubernetes:extensions:Ingress internal-rpc updating error: No matching service found for ingress rule: ""
 ~  kubernetes:extensions:Ingress internal-rpc updating error: No matching service found for ingress rule: ""
 ~  kubernetes:extensions:Ingress internal-rpc updating error: No matching service found for ingress rule: ""
 ~  kubernetes:extensions:Ingress internal-rpc updating error: No matching service found for ingress rule: ""
 ~  kubernetes:extensions:Ingress internal-rpc updating error: No matching service found for ingress rule: ""
 ~  kubernetes:extensions:Ingress internal-rpc updating error: No matching service found for ingress rule: ""
 ~  kubernetes:extensions:Ingress internal-rpc updating error: No matching service found for ingress rule: ""
 ~  kubernetes:extensions:Ingress internal-rpc updating error: No matching service found for ingress rule: ""
 ~  kubernetes:extensions:Ingress internal-rpc updating error: No matching service found for ingress rule: ""
 ~  kubernetes:extensions:Ingress internal-rpc updating error: No matching service found for ingress rule: ""
 ~  kubernetes:extensions:Ingress internal-rpc updated error: No matching service found for ingress rule: ""
@ Updating...| / - \ | /                  prebuilt:Deploy ethereum

Does Pūlumi implement a Cloudfront Invalidation? I can’t find it in the API docs… https://docs.aws.amazon.com/cloudfront/latest/APIReference/API_CreateInvalidation.html

Running into this error

Plan apply failed: deleting urn:pulumi:docs::arcusdocs::aws:cloudfront/distribution:Distribution::cdn: error updating CloudFront Distribution (E1QDDY8Y64KZAE): PreconditionFailed: The request failed because it didn't meet the preconditions in one or more request-header fields.

while trying destroy

aws:cloudfront:Distribution (cdn)

What could be the reason?

When a Target or Policy type requires a

resourceId

, how do you obtain it? For example:

let ddb_tbl = new aws.dynamodb.Table("mytable", ...);
let scalable_target = new aws.appautoscaling.Target('my_scalable_target', {
  resourceId: 'table/' + ddbl_table.name
});

The resourceId setting above does not work.

Ok, nvm, figured it out:

resourceId: ddb_tbl.name.apply( id => `table/${id}`)

My app.pulumi.com dashboard for my stack no longer shows any Status links to AWS under the RESOURCES tab. I confirmed that all my resources have been created. 🙂

How do I deal with this

error: the current deployment has 1 resource(s) with pending operations:
  * urn:pulumi:docs::xyz::aws:cloudfront/distribution:Distribution::cdn, interrupted while deleting`?

Hi, anyone have any tips or work arounds for

require("@pulumi/docker").Image

docker images and Github Actions workflows? Using this resource fails due to github disallowing

docker image inspect

for some reason. Someone else has created an issue here https://github.com/pulumi/pulumi-cloud/issues/681. This error makes the otherwise awesome example https://github.com/pulumi/actions-example-gke-rails sort of sad since it doesn't work. Was this not an issue at the time of writing?

thought I’d give a random shout out to the pulumi team. I’ve been playing with it here and there over the last month and gotta say I really believe in what Pulumi is trying to accomplish. I think it’s the right approach. Also, I’m getting some nostalgia watching Pulumi the last few months from the outside. reminds me of a startup i was at for a while (Appcelerator): How the company is ramping up.  How Pulumi is approaching the product from a grass roots POV.  CTO jumping on live coding sessions on Youtube to show off things.  There’s a coolness factor to it.  Fits a need. seems to have a good dev culture around it. Everything on Github, etc etc etc Keep it up y’all!

Want the fastest way to provision an EKS cluster on AWS? Who doesn't? @white-balloon-205 discusses the

@pulumi/eks

component and getting provisioned quickly and effectively https://blog.pulumi.com/the-fastest-path-to-deploying-kubernetes-on-aws-with-eks-and-pulumi

I'm testing out k8s with Pulumi. I added this to my code:

const nginx2 = new k8s.helm.v2.Chart("nginx-reverse-proxy", {
    chart: "bitnami/nginx",
    repo: "stable",
    version: "2.1.2",
    values: {
        vhost: nginxConfStr
    }

}, {providers: {kubernetes: cluster.provider}});

and I receive this error message. I have no idea what this means 😕

/home/kenny/compute_software/infrastructure/pulumi-k8s-src/node_modules/got/source/create.js:61
        got.stream = (url, options) => got(url, {...options, stream: true});
                                                 ^^^
    SyntaxError: Unexpected token ...
        at Object.exports.runInThisContext (vm.js:53:16)
        at Module._compile (module.js:513:28)
        at Object.Module._extensions..js (module.js:550:10)
        at Module.load (module.js:458:32)
        at tryModuleLoad (module.js:417:12)
        at Function.Module._load (module.js:409:3)
        at Module.require (module.js:468:17)
        at require (internal/module.js:20:19)
        at Object.<anonymous> (/home/kenny/compute_software/infrastructure/pulumi-k8s-src/node_modules/got/source/index.js:3:16)
        at Module._compile (module.js:541:32)

How can I use pulumi non-interactively, e.g. in a gitlab CI pipeline?

are configuration values limited to

namespace:value

or can they support multiple levels such as

namespace:section:value

?

Does anyone know if pulumi supports alb-ingress-controller creation at the moment?