Anyone know why a AWS policy fails to be deployed when only the description changes?

Hi guys, I have a question. I have two projects, with S3 backend. Project A with stack default and Project B with stack dev. Now I want to get the stack output of Project A in Project B. How can I achieve this? Thanks in advance.

Had a question on install - what is a good way to run curl -fsSL https://get.pulumi.com | sh to install pulumi into a specific directory

Like with sdkman you can specifically set the SDKMAN_HOME to then run a similar sdkman install into that dir. Is there something similar for pulumi?

I know I could download and unpack the tar.gz file into a directory but I would need to know the version number every time as part of a bash script - thus would be very helpful to be able to run the setup script to install into /opt where I keep my tools

Thanks for your help

Any idea why a nodepool is trying to be replaced and the only thing the diff shows different is the provider?

is the @pulumi/azure 19.4 broken? it seems to rely on @azure/ms-rest-js and its throwing all sorts of errors

Hi, has anyone tried to run pulumi in docker:dind? I tried to run it but it seems like it does not recognize the pulumi executable

so, you're using the pulumi image from inside a container running the

docker:dind

image?

(the topology of what you're doing is unclear)

pulumi preview/up

just exits with code 255 and no error, not preview what do I do wrong? index.ts:

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

const config = new pulumi.Config("gcp-bootstrap");

// Create a GCP resource (Storage Bucket)
const gke = new gcp.organisations.Project("gke01", {
    orgId: config.require("organisation")
});

// Export the DNS name of the bucket
export const gkeId = gke.id;

tail of

pulumi preview

Logging in using access token from PULUMI_ACCESS_TOKEN
Previewing update ($CORP/prod):

Permalink: <https://app.pulumi.com/$CORP/gcp-bootstrap/prod/previews/242b9dd0-b832-4f99-94fd-de87398528ca>

Was running no problem earlier. Then ran

pulumi preview

, froze the console, broke out and this started to happen. A reboot didn't fix it.

This will probably seem an odd question, but is there any way to use the pulumi API’s without the declarative plan and apply bits? For example, I’d like to just have a program that runs

const deployment = new k8s.apps.v1.Deployment(...)

and have it create it right then and there.

Does pulumi/gke drain the nodes when doing a replacement on the node pool in a way that a PDB would apply? Because when pulumi goes to replace a pool, my pods go down even though I have PDBs.

having exactly same probelm as in https://github.com/pulumi/pulumi/issues/2651 but with GCP provider 😕

I am pretty sure problem is in custom CA certificates we have to use and that error is not properly propagated 😞

does anyone know how kubernetes namespaces work with the

getResourceProperty()

method? All the examples I’ve seen look like this:

guestbook.getResourceProperty("v1/Service", "frontend", "status")

but I get an exception unless I prefix the resource name with the namespace:

mysql.getResourceProperty("v1/Service", "idm-mysql", "spec")
...
TypeError: Cannot read property 'spec' of undefined

whereas this works:

mysql.getResourceProperty("v1/Service", "pulimi-test/idm-mysql", "spec")

what am I missing?

the pulumi kubernetes provider IDs are a normal kubernetes reference so yeah namespace/object

if you dont specify the namespace it's assumed to be 'default'

ah ok - so in examples like this everything is bound to the

default

ns? https://github.com/pulumi/kubernetes-the-prod-way/blob/master/services/wordpress/index.ts

yeah exactly

ok, cheers - is there a good pattern for managing this?

pulumi config set k8s-namespace pulumi-test

, then pepper

config.require()

throughout my resource definitions?

i'm not sure tbh - i believe there's a kube way of creating a context which can specify a namespace and if so, i think the pulumi provider probably supports that too but i've not looked

yep: https://github.com/pulumi/pulumi-kubernetes/blob/master/sdk/nodejs/provider.ts#L14

ok, thanks!

ah neat

ok, today's github action's announcement is pretty exciting for pulumi users. Watch for the rollout in the next few weeks.

Hi all, is there any good workflow for local development of http lambda functions? Similar to what

serverless-offline

offers? I'm new to Pulumi and excited to work on this!!

js, python, or go?