faint-article-37196
11/30/2022, 10:01 AMproud-city-30820
11/30/2022, 10:28 AMclever-soccer-98174
11/30/2022, 11:00 AMimport * as aws from "@pulumi/aws";
import * as apigateway from "@pulumi/aws-apigateway";
// Create a Lambda Function
const helloHandler = new aws.lambda.CallbackFunction("hello-handler", {
callback: async (ev, ctx) => {
return {
statusCode: 200,
body: "Hello, API Gateway!",
};
},
});
// Define an endpoint that invokes a lambda to handle requests
const api = new apigateway.RestAPI("api", {
routes: [
{
path: "/",
method: "GET",
eventHandler: helloHandler,
},
],
});
export const url = api.url;
But unfortunately I’m stucked with this error :
error: update failed
aws:apigateway:RestApi (api):
error: 1 error occurred:
* creating urn:pulumi:dev::meeting-integrations::aws-apigateway:index:RestAPI$aws:apigateway/restApi:RestApi::api: 1 error occurred:
* error creating API Gateway specification: BadRequestException: Errors found during import:
Unable to put integration on 'GET' for resource at path '/': Invalid ARN specified in the request
Do you have any knowledge about this issue?millions-parrot-88279
11/30/2022, 2:34 PMmany-helicopter-89037
11/30/2022, 4:43 PMfamous-eve-66520
11/30/2022, 6:20 PMhallowed-australia-10473
11/30/2022, 9:47 PMbrief-pencil-59807
12/01/2022, 11:45 AMVirtual machine scale set
via pulumi, can someone direct me the pulumi function or example how to do this?brief-pencil-59807
12/01/2022, 11:52 AMcolossal-flower-75468
12/01/2022, 3:45 PMfreezing-activity-93019
12/01/2022, 4:48 PMDiagnostics:
pulumi:pulumi:Stack (pulumi-kubernetes-pulumi-kubernetes):
error: an unhandled error occurred: program exited with non-zero exit code: 2
panic: fatal: An assertion has failed: {<nil> <nil> <nil> <nil> <nil> <nil> <nil> <nil> <nil> <nil> flux-system flux-system <nil> <nil> <nil> <nil>}: cannot assign v1.objectMetaPtrType to v1.ObjectMeta
goroutine 42 [running]:
Source code: https://gist.github.com/hbjydev/ba680822b8652812b1c4d238ce5f14f6acceptable-tent-31739
12/01/2022, 4:51 PMgorgeous-architect-28903
12/01/2022, 6:26 PMWithResourceOptions([dependencyResource, providers], func() {
ResourceOne(ctx, name, ...)
ResourceTwo(ctx, name, ...)
})
And have them all automatically get the dependency without having to type it 5 times, or move them around in the tree. Kind of like registering a stack transformation, but not globally.bored-activity-40468
12/01/2022, 9:07 PMfaint-article-37196
12/02/2022, 2:59 AMicy-controller-6092
12/02/2022, 4:38 AMexpected runtime_environment to be one of [SQL-1_0 FLINK-1_6 FLINK-1_8 ZEPPELIN-FLINK-1_0 FLINK-1_11 FLINK-1_13 ZEPPELIN-FLINK-2_0], got FLINK-1_15.
Is there any way I can get around this locally? The remote API will accept the new value, it’s just local validation in Pulumi that is failing. e.g. maybe there is a flag I can use to turn off this local-only client-side validation?agreeable-orange-1262
12/02/2022, 11:05 AMmost-mouse-38002
12/02/2022, 12:05 PMpulumi preview --json --non-interactive
documented anywhere? I just can’t find it.thousands-lizard-52998
12/02/2022, 12:06 PMdamp-painting-47843
12/02/2022, 2:56 PMgreen-kilobyte-86931
12/02/2022, 3:17 PMgifted-room-26715
12/02/2022, 6:18 PMbillowy-nightfall-59212
12/02/2022, 8:59 PMpulumi up
we are running into this error could not query backend for stacks: unexpected end of JSON input
microscopic-piano-27908
12/02/2022, 11:31 PMpulumi up
which will sometimes either take 20+ minutes or time out.hallowed-australia-10473
12/03/2022, 11:03 PMpulumi up
?blue-leather-96987
12/04/2022, 12:01 AMcold-cpu-48402
12/04/2022, 9:12 AMgifted-fall-44000
12/04/2022, 10:48 PMmelodic-branch-55999
12/05/2022, 8:11 AMec2-user 31942 14939 0 Nov30 ? 00:00:00 [pulumi-resource] <defunct>
ec2-user 31943 14939 0 Nov30 ? 00:00:00 [pulumi-resource] <defunct>
ec2-user 31944 14939 0 Nov30 ? 00:00:00 [pulumi-resource] <defunct>
ec2-user 31945 14939 0 Nov30 ? 00:00:00 [pulumi-language] <defunct>
ec2-user 31946 14939 0 Nov30 ? 00:00:00 [pulumi-resource] <defunct>
ec2-user 31947 14939 0 Nov30 ? 00:00:00 [pulumi-resource] <defunct>
the count of above process keeps on increasing and reaches the cgroups limit set at
/sys/fs/cgroup/pids/kubepods/pids.max
due to this there is shortage of resource in the node and the CNI(aws-node) keeps on restarting due to Livlinessprobe failure.
What should we do in overcome this? Any help will be greatly appreciated, this is blocking our GA.bitter-city-18176
12/05/2022, 10:47 AMOriginRequestPolicy
or a CachePolicy
to a CloudFront Distribution