ah I just realized you're referring to the python module

How do I fix the problem with pulumi saying that aws:region is not configured even though it is:

Diagnostics:
  aws:ec2:VpcPeeringConnection (vpc-peering-connection):
    error: 1 error occurred:
    	* missing required configuration key "aws:region": The region where AWS operations will take place. Examples are us-east-1, us-west-2, etc.
    Set a value using the command `pulumi config set aws:region <value>`.

I am creating a config with

pulumi.Config()

and it seems that it triggers the error

I seem to still be having some very weird issues from the k8s auto-aliasing change (previously mentioned here https://pulumi-community.slack.com/archives/C84L4E3N1/p1570297147325000) Here’s a super simple example where I”m seeing weirdness: https://gist.github.com/timmyers/adc57e4dca7dc7a3c14a310d5f4ce6a6 The program consists of a namespace and a deployment. I have those both applied successfully,

pulumi up

shows no diff. Then I uncomment the service object and try to

pulumi up

again. The first run crashed, the second one gives a very odd unexpected diff.

I'm having issues with one Fargate service in a public subnet talking to another which is behind an internal alb in a private subnet. They're both in the same VPC created using awsx and have routes which cover the entire CIDR block of the VPC set to local.

Any idea if using https://github.com/aws/jsii with Pulumi work?

I think theres a bug in gcp.compute.Address, if you leave out Region its suppose to be a Global Address type, if you specify region its suppose to be a regional address type. But if I leave it out, it's still filling in Region so it's impossible to create a Global address type.

Hi all. Is there a way to call async functions inside pulumi code (Typescript) ? I often find it useful to execute other tasks (write a file, call an api, etc) based on resources created by pulumi. In another runtime this wouldn't be an issue - but many node packages are async only - and I have not been able to use them with pulumi. Anyone had success with this?

Is there a simple way of moving resources between stacks? I am trying to split big infrastructure stack into a "micro-stacks", because big number of resources makes pulumi very slow.

When will @pulumi/pulumi 1.3.2 be published to npm?

@worried-engineer-33884 we are looking at releasing later today (Seattle time)

pulumi destroy

on an AKS cluster with custom networking (referencing a self-created subnet from the aks cluster) resulted in an error of wrong destroy order (subnet cannot be deleted as there are resources in it) So pulumi lost the aks cluster from the pulumi state but it still exists in Azure. Adding a

dependsOn

seems unnecessary as the chain should already exist due to the reference of the subnet in the aks cluster creation. How to clean that up?

pulumi up

will create an additional cluster as there is no more reference in the pulumi state…

Hello, I'm writing an integration test with Typescript and need to wait for a Helm Chart to complete and the associated resources to be completed. I'm at a loss for how to do that. Anyone have any pointers?

I have a program using

aws.getCallerIdentity

that was working and has somehow now stopped. I changed the program to just

import * as pulumi from '@pulumi/pulumi';
import * as aws from '@pulumi/aws';

(async () => {
  console.log('start')
  console.log(await aws.getCallerIdentity());
  console.log('end')
})();

and it hangs on

aws.getCallerIdentity()

Any idea what could have happened?

I'm trying to enable CORS on an api gateway endpoint using awsx, but am unable to find an example in the docs of how to do so.

new awsx.apigateway.API(`firebaseAuth-${stack}`, {
	routes: [
		{
			path: '/',
			method: 'POST',
			apiKeyRequired: true,
			eventHandler: new aws.lambda.CallbackFunction(`firebaseAuth-${stack}`, {
				callback: (event, _, cb) =>
					cb(null, {
						statusCode: 200,
						headers: {
							'Access-Control-Allow-Origin': '*',
						},
						body: handler(event),
					}),
			}),
		},
	],
})

Is there a simple way to add cors headers to the preflight response in the awsx implementation?

Why is it that anytime I use a helm chart I get

[Can't preview] all chart values must be known ahead of time to generate an accurate preview.

during preview?

Is there a way to invoke

task.run({ cluster });

on a FargateTaskDefinition at the top-level of our pulumi program during update? We are trying to run a one-off task inside a container, without needing lambda like in https://www.pulumi.com/docs/guides/crosswalk/aws/ecs/#running-fire-and-forget-tasks .

Terraform has input variables. That allows user inputs value when run commands. Is there similar solution for Pulumi?

Many thanks for the new targeted update/destroy features in the last few releases. This has made my life a lot easier! 👍

Is there a plan to support providers implemented in a language other tan golang (e.g. typescript)?

I've updated to latest everything and hit my first hang issue (during preview) running

pulumi up

with no significiant changes Ubuntu 18.04.3, nodejs 12.11.1, @pulumi/pulumi 1.3.4, @pulumi/aws 1.7.0, @pulumi/kubernetes 1.2.3 Not sure but is the hang issue supposed to be fixed now?

So I am getting this error for some reason when running from GitHub. It's very odd, my other repos work but this one which I just created throws this error. I have no idea why...Any thoughts?

I follow the official example aws-ts-stackreference (https://github.com/pulumi/examples/tree/master/aws-ts-stackreference) with self-managed backend (locally on filesystem) (https://www.pulumi.com/docs/intro/concepts/state/#self-managed-backend). If I use the default directory

file://~

for all projects and run

pulumi up

for

company

project then

department

project, Pulumi will delete the

company

stack and create stack for

department

. If using Pulumi Backend Service, this statement works:

new pulumi.StackReference('clstokes/aws-ts-stackreference-company/dev')

where

clstokes

in the example is the Pulumi Backend Service username,

aws-ts-stackreference-company

is the project name and

dev

is the current stack. If I set backend url, so each project has a separated

.pulumi

at it's root directory

Pulumi.yaml
backend:
  url: file://./

Now, how can I get the stack reference of

company

or

department

in

team

project:

new pulumi.StackReference('???')

?

new pulumi.StackReference('clstokes/aws-ts-stackreference-company/dev')

will produces error:

pulumi:pulumi:StackReference (clstokes/aws-ts-stackreference-company/dev):
    error: Preview failed: unknown stack "clstokes/aws-ts-stackreference-company/dev"

hi, is it possible to move resources between projects without recreating them? I know I can import a resource from an other project, but I can't remove it from the old one, because I don't want to recreate it, so I have to manually remove from the state file. Is there a better, more automated and less error prone option?

Do I have to do something different for GCP when using StackReference to generate the provider from the kubeconfig? Because it doesn't seem to work for me...

What is the best place to report bugs and feature requests for the pulumi console? I requested a while ago you guys to open a github project which is just used for issue reporting regarding the console (to be consistent with all other components), but no luck yet 😞 . cc @gentle-diamond-70147

Sorry if this is a dumb question. I am collaborating on an open source project with a couple others. Would it be against the terms and conditions to use the community edition and share the credentials between users?

I am trying to "adopt" an aks cluster, but I cannot seem to match the "servicePrincipal" secret. Is there a secret to this?

Perhaps I’ve missed the message, in which case please disregard. I noticed that Node.js 8.10 will reach EOL end of this year so perhaps a note in the docs would be useful? Something like “Soon to be deprecated” for https://www.pulumi.com/docs/reference/pkg/nodejs/pulumi/aws/lambda/#NodeJS8d10Runtime ? Just a thought.