straight-insurance-27894
11/20/2019, 8:21 PMminiature-potato-84713
11/20/2019, 8:51 PMruntime: 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?early-intern-90238
11/20/2019, 10:12 PMearly-intern-90238
11/20/2019, 10:12 PMearly-intern-90238
11/20/2019, 10:13 PMearly-intern-90238
11/21/2019, 1:13 AMearly-intern-90238
11/21/2019, 1:14 AMearly-intern-90238
11/21/2019, 1:16 AMearly-intern-90238
11/21/2019, 1:18 AMearly-intern-90238
11/21/2019, 1:24 AMadventurous-garage-59192
11/21/2019, 2:49 AMelegant-twilight-2745
11/21/2019, 12:18 PMnice-cat-91582
11/21/2019, 12:39 PMPulumi.dev.yaml
? Seems like that would all be stored in Pulumi Cloudplain-eye-9759
11/21/2019, 12:57 PMencryptionsalt: v1:xyz==
config:
my-project:secretConfig:
secure: v1:DtxM
Doesn't this pose a security challenge?
In what other ways can this be done?colossal-plastic-46140
11/21/2019, 2:06 PMincalculable-engineer-92975
11/21/2019, 2:08 PMelegant-twilight-2745
11/21/2019, 2:50 PMelegant-twilight-2745
11/21/2019, 3:10 PMnice-guitar-97142
11/21/2019, 3:52 PMpulumi up
?nice-guitar-97142
11/21/2019, 3:52 PMelegant-twilight-2745
11/21/2019, 4:41 PMboundless-monkey-50243
11/21/2019, 4:43 PMpulumi 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?bright-apple-15972
11/21/2019, 7:33 PMswift-painter-31084
11/21/2019, 7:46 PMdelightful-dawn-43855
11/21/2019, 10:33 PMKind = "Elastic",
Sku = new PlanSkuArgs
{
Tier = "ElasticPremium",
Size = "EP1",
Capacity = 1
}
//properties for "maximumElasticWorkerCount": 2 doesn't exist yet
full-dress-10026
11/22/2019, 12:49 AMerror: 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.ambitious-ram-5811
11/22/2019, 12:53 AMpulumi refresh
or if that doesn't work, manually deleting the thing it Doesn't Like, then running pulumi refresh
full-dress-10026
11/22/2019, 1:10 AMeks.NodeGroup
already do that?full-dress-10026
11/22/2019, 1:17 AMfull-dress-10026
11/22/2019, 1:18 AMpulumi 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