THere are no other instances of node or pulumi running. It's a fresh reboot. All yarn files match. And I can't find anything about this on the net. Chris Duck is running the same setup and is not having this issue. Have you see this issue?

I’m using a Javascript function for Lambda on Edge, with

runtime: aws.lambda.NodeJS8d10Runtime,

but then received an email from AWS that that runtime will be obsoleted:

your AWS Account currently has one or more Lambda functions using Node.js 8.10, which will reach its EOL at the end of 2019.

So I wanted to switch to then next version but

error TS2551: Property 'NodeJS10dXRuntime' does not exist on type 'typeof import("/.../node_modules/@pulumi/aws/lambda/i...'. Did you mean 'NodeJS6d10Runtime'

Note that

NodeJS10dXRuntime

is still documented here: https://www.pulumi.com/docs/reference/pkg/nodejs/pulumi/aws/lambda/#NodeJS10dXRuntime So I changed to using the string

"nodejs10.x"

which didn’t work

error: aws:lambda/function:Function resource 'language-redirect' has a problem: expected runtime to be one of [dotnetcore1.0 dotnetcore2.0 dotnetcore2.1 go1.x java8 nodejs4.3 nodejs4.3-edge nodejs6.10 nodejs8.10 provided python2.7 python3.6 python3.7 ruby2.5], got nodejs10.x

and then went back to

runtime: "nodejs8.10"

which is the one that will be obsoleted soon. So… what should I do here?

There is some serious jank with Release Channels

for instance there is no way to define the latest version of a Release Channel for the initial create of your cluster with a release channel

you would expect there to be a filter clause on getEngineVersions something like channel, but no...

Ok I found an interesting problem I think

a pulumi refresh doesn't pull stack reference info, so if you share your provider via a stack and your nodes change because of a replacement in a microstack, when you attempt to do a pulumi update in another microstack that depends on the provider from a stack reference you get a timeout error

It would be interesting to let you run a command to update certain stack references

I guess you can do this via --target

so yes that works great, but its a pain in the butt to do it that way...

Hello, I'm getting `System.InvalidOperationException: Expected System.String but got System.Collections.Immutable.ImmutableArray`1[[System.Object, System.Private.CoreLib, Version=4.0.0.0, Culture=neutral, PublicKeyToken=7cec85d7bea7798e]] deserializing Pulumi.Azure.AppService.AppService.appSettings` after updating to Pulumi 1.6.0

How to delete and start login account all over again

This feels like a dumb question... but am I supposed to commit my stack config files, like

Pulumi.dev.yaml

? Seems like that would all be stored in Pulumi Cloud

This builds on Joe's question: In the stack config files, the encryption salt and the secret are both saved in the file like so:

encryptionsalt: v1:xyz==
config:
  my-project:secretConfig:
    secure: v1:DtxM

Doesn't this pose a security challenge? In what other ways can this be done?

Good Morning. We are working on the CI pipeline for adding a pulumi preview check prior to merging a PR. It currently looks like when selecting --stack on the command line one is not able to do stack init automatically/ if the stack file is already committed to git? I was wondering if anyone had suggestions that work with a s3 backend

Can we please, please, please get an event notification or overall Promise or defer mechanism that fires when a 'pulumi up' is finished? We're jumping through hoops to have integration tests when a pulumi run is done. In most cases we wrap individual tests in 'apply' or 'all' but that doesn't always work. We just had a case where a test would start before a model was assigned to a variable so we couldn't use either approach and had to switch to an event emitter to hold the test back. This seems ridiculous. Why can't we get an overall 'pulumi up/preview/destroy' is done, run your follow-on code now?

Within corporate environment under ADMIN mode Powershell, I was able to login and pulumi whoami recognized username, but pulling down from existing project created previously outside of corporate environment with: > pulumi new aws-typescript -s USERNAME/aws-typescript/dev > > ENTER to log in using your browser > > but opens: "Pulumi doesnt support this version of Microsoft Internet Explorer" please consider upgrading. > > and I dont think I can upgrade at Microsoft IE at clients site??? Please advise if anyone I am sure has faced this situation as well as it is asking for Windows Security iexplore credentials

Can Pulumi and Terraform both exist within a project? So that if someone still wants to work with Terraform and deploy to AWS, and I use Pulumi to deploy to the same AWS cluster? is that ok?

Can I have Pulumi read the state of current infrastructure and use that as a starting point for the first

pulumi up

?

specifically with the azure provider, if that matters

With source code and IaaC within the same project and residing in pulumi, if security is concerned just have IaaC inside pulumi and source code in Gitlab? But then separately into different repos defects the purpose of having source and IaaC nicely together as one...?

S3 backend issue: so for reasons I...do not particularly love, we're using multiple AWS accounts that access the same shared S3 bucket for stacks. When I run

pulumi stack ls

as the bucket owner, not every stack created by other accounts in that bucket show up. (Some do. Not all.) When I do

aws s3 ls

, however, the JSON files do appear in the list. I can't read them as the bucket owner, however, and get a 403 on HeadObject/GetObject. My initial expectation was an ACL problem, but I've since run

aws s3 cp

across the entire bucket setting everything to bucket-owner-full-control and while that has in the past worked occasionally (for reasons I am not fully sure of), it's not working now. 1. How can I unjam myself? 2. My intuition is that this is a problem with the S3 client used by Pulumi. What steps can I take to prevent it from happening again?

can pulumi make or use LVM block devices? And, if the AMI being used already has volumes attached to it, would pulumi respect those volumes?

https://www.pulumi.com/docs/reference/pkg/nodejs/pulumi/aws/codedeploy/ I'm looking for information on the "TrafficRoutingConfig" block for AWS code deploy. Every reference to it says "is documented below", but there is nothing below there or elsewhere in the #docs

I've been trying pulumi (C#) to deploy to Azure, really easy to get going and it's been a pleasure so far. Microsofts recently released Azure functions premium plan (4:th of november), to my surprise I was able to create the resource in pulumi right away(!), but i'm missing one important property in the PlanArgs, MaximumElasticWorkerCount, i'm guessing it should go in the properties section? This is really "icing on the cake" considering that it's been newly released and all, but would appreciate an indication on when it can be available.

Kind = "Elastic",
				Sku = new PlanSkuArgs
				{
					Tier = "ElasticPremium",
					Size = "EP1",
					Capacity = 1
				}
				//properties for "maximumElasticWorkerCount": 2 doesn't exist yet

I have somehow gotten into a situation where Pulumi thinks it needs to delete a launch configuration but can't.

error: Plan apply failed: deleting urn:pulumi:dev::vm-scaler::eks:index:Cluster$eks:index:NodeGroup$aws:ec2/launchConfiguration:LaunchConfiguration::k8s-dev-ng-nodeLaunchConfiguration: error deleting Autoscaling Launch Configuration (k8s-dev-ng-nodeLaunchConfiguration-b5215a6): ResourceInUse: Cannot delete launch configuration k8s-dev-ng-nodeLaunchConfiguration-b5215a6 because it is attached to AutoScalingGroup k8s-dev-ng-e37cdc2e-NodeGroup-6186KPAWLIPL
    	status code: 400, request id: 1a10ee34-0cc1-11ea-afde-8d216d809694

This occurred after a

pulumi up

failed with this error:

error: Plan apply failed: 1 error occurred:
    	* updating urn:pulumi:dev::vm-scaler::eks:index:Cluster$eks:index:NodeGroup$aws:cloudformation/stack:Stack::k8s-dev-ng-nodes: UPDATE_ROLLBACK_COMPLETE: ["MinInstancesInService must be less than the autoscaling group's MaxSize"]

Is there a way to get myself unstuck from this? Every

pulumi up

now fails with the former error.

I usually get out of these situations by trying

pulumi refresh

or if that doesn't work, manually deleting the thing it Doesn't Like, then running

pulumi refresh

Can you create EKS Managed Node Groups (https://docs.aws.amazon.com/eks/latest/userguide/managed-node-groups.html)? Or does

eks.NodeGroup

already do that?

@ambitious-ram-5811 No dice 😞

When trying to delete the problem resource, Pulumi thinks it doesn't exist:

pulumi state delete urn:pulumi:dev::vm-scaler::eks:index:Cluster$eks:index:NodeGroup$aws:ec2/launchConfiguration:LaunchConfiguration::k8s-dev-ng-nodeLaunchConfiguration
 warning: This command will edit your stack's state directly. Confirm? Yes
error: No such resource "urn:pulumi:dev::vm-scaler::eks:index:Cluster:index:NodeGroup:ec2/launchConfiguration:LaunchConfiguration::k8s-dev-ng-nodeLaunchConfiguration" exists in the current state