but, in the event of DR, I'll need it to 'reappear' empty

I'm assuming this is what

protect

will do

Is the RandomPassword result supposed to be treated as a Secret? I am seeing it as plain text in the logs and in the output: export const password = new RandomPassword("password", { length: 20 }).result; Outputs: password: "&3MHv-kbBv&AY-wP=ShK"

There’s an open issue for this. It is currently not treated as one. Let me see if I can find it for you

Semi related: https://github.com/pulumi/pulumi/issues/3333

hmm. that kinda kills the ability to use StackReference to break up the infrastructure. I need to share the kubeconfig. Is there any way to destroy a stack without destroying the items it imported? (I was able to my stacks up so that a second stack imported the ids of the first stack, but then destroying the second stack also destroys the imported resources. )

ok, one more: I am using this example: https://github.com/pulumi/examples/blob/16958e3f9ca4d8921e773921ae5f977861a3449d/azure-ts-aks-keda/cluster.ts Creating privatekey const sshPublicKey = new tls.PrivateKey("keda", { algorithm: "RSA", rsaBits: 4096, }).publicKeyOpenssh; and passing the sshPublicKey to cluster's linxProfile: linuxProfile: { adminUsername: "aksuser", sshKey: { keyData: sshPublicKey, }, }, This was working fine for a while, but now I always get the following error: Failure sending request: StatusCode=400 -- Original Error: Code="InvalidParameter" Message="The value of parameter linuxProfile.ssh.publicKeys.keyData is invalid. Please see https://aka.ms/aks-naming-rules for more details." Target="linuxProfile.ssh.publicKeys.keyData" Has anyone seen this before? I cannot figure out how to get past this issue.

Is there a way to do a kubectl rollout restart?

Does anyone know how to get out of the

snapshot integrity failure; refusing to use it

state?

can’t wait pulumi-awsx:v0.18.13 on npm. I really need this:

secrets

property to

awsx.ecs.Container

to allow injecting sensitive data into a container.

Is there any way to control the AWS Lambda runtime for timers from

@pulumi/cloud-aws

? Getting emails from AWS that Node 8 runtime is going to be EoL so I want to upgrade to Node 10 runtime but there doesn't seem to be a way with Pulumi to specify

My pulumi up's are hanging on

debug: Trying to get account information via sts:GetCallerIdentity

...is there anything past

--debug

to use to investigate why this is happening?

@white-balloon-205 "What does

which python3

report for you?" which isn't recognized in Windows Terminal / Powershell PS C:\Users\g> python Python 3.8.0 (tags/v3.8.0:fa919fd, Oct 14 2019, 193750) [MSC v.1916 64 bit (AMD64)] on win32

I have multiple pulumi stacks in a project, and after being able to deploy

stack1

, I’m getting and error when trying to deploy

stack2

. I’ve exported my environment via

export AWS_PROFILE=staging

and logged into the appropriate s3 endpoint, but I’m getting the following error. Does anyone know what I could be doing wrong?

Error: invocation of aws:cloudformation/getStack:getStack returned an error: unable to discover AWS AccessKeyID and/or SecretAccessKey

.

Does a code sample exist describing how to manage docker containers directly on EC2 instances (or any host)?

Is it convention to export the VPC object when you have a multi-stack Pulumi setup? Or will that pretty much cause everything inside the VPC to be exported?

Where's Pulumi at with regards to

terraform import

-style functionality? I have to do some pretty broad surgery on our environment and would rather move our stuff over while I'm at it.

Trying to define a policy for Gated Deployments that relates AWS S3 BucketPublicAccessBlocks to Buckets. Haven't been able to figure out a way to check that a BucketPublicAccessBlock exists for each bucket. Tried to get instances of publicAccessBlocks and compare bucket ids too, but I don't think it works.

I’m in the middle of trying to set up an autoscalinggroup for an existing ecs cluster. It was having issues with something being in ROLLBACK_COMPLETE state so I did a refresh, but now I get a

panic: fatal: An assertion failed

error. I will post the stack trace in a thread reply

May ... I've not had a build green since May 😞

I'm trying to use a secret as the kubeconfig for the k8s.Provider, but it keeps failing. Does anyone know what I am doing wrong? 😞

const kubernetesProvider = new k8s.Provider("metrics", {
  kubeconfig: config.requireSecret("kubeconfig")
});

I'm now doing

pulumi config get kubeconfig > kubeconfig

and loaded this file during

pulumi up

. Please tell me there's a better way 🙂

OK. Found some sort of problem 😕

const kconfig = fs.readFileSync("../kubeconfig").toString();
const kubernetesProvider = new k8s.Provider("metrics", {
  kubeconfig: kconfig
});

Fails:

error: unable to load Kubernetes client configuration from kubeconfig file: invalid configuration: no configuration has been provide

But

kubectl get pods -n community --kubeconfig=./kubeconfig

works 😞

Trying to create a lambda for handling S3 object creation:

transcriptionJobs.bucket.onObjectCreated('publish', async ev => {
  const s3Client = new aws.sdk.S3()
  const kinesisCliet = new aws.sdk.Kinesis()
  for (const { s3: { bucket, object } } of ev.Records || []) {
    console.log({ bucket, object })
  }
})

and getting an error:

Error: failed to register new resource publish [aws:lambda/function:Function]: 2 UNKNOWN: failed to compute asset hash: asset path 'node_modules/@lemonade/infra-common' is a directory; try using an archive

Arch AUR updated to 1.4.0 🙂 https://aur.archlinux.org/packages/pulumi-bin/

Following this guide: https://www.pulumi.com/docs/guides/crosswalk/aws/ecs/#creating-an-auto-scaling-group-for-ecs-cluster-instances I am calling

createAutoScalingGroup

on an

awsx.ecs.Cluster

. I get the error

Property AvailabilityZones cannot be empty

. I don’t see an option for setting

availabilityZones

through

createAutoScalingGroup

.

Is there an easier way to copy a stack config with secrets? I am creating a new stack and right now I just copy the yaml and redo all the secret values with

pulumi config set --secret ...

what is the Windows PS equivalent to the instructions at https://www.pulumi.com/docs/get-started/aws/review-project/