mysterious-belgium-44686
06/06/2021, 3:59 PMmelodic-car-16900
06/06/2021, 7:41 PMancient-oil-47691
06/07/2021, 5:47 AMbrave-winter-60074
06/07/2021, 9:24 AMbumpy-agent-19616
06/07/2021, 11:32 AMgorgeous-eye-54797
06/07/2021, 12:21 PMechoing-zebra-28421
06/07/2021, 7:07 PMechoing-zebra-28421
06/07/2021, 7:09 PMbored-table-20691
06/07/2021, 11:44 PMhappy-angle-19851
06/08/2021, 5:29 AMbored-planet-52144
06/08/2021, 12:45 PMwitty-airport-81009
06/08/2021, 1:28 PMechoing-zebra-28421
06/08/2021, 2:11 PMimport * as aws from "@pulumi/aws";
import * as awsx from "@pulumi/awsx";
// Look up an existing Lambda Function by ID, so that we can get its ARN. (If we knew the ARN ahead
// of time, this would not be necessary, we can just use it in the URI below.)
const handler = aws.lambda.Function.get("get-handler", "your_lambda_id");
// Define a GET endpoint that invokes our Lambda Function-based handler.
const api = new awsx.apigateway.API("example", {
swaggerString: handler.arn.apply(arn => JSON.stringify({
"swagger": "2.0",
"info": {
"title": "example",
"version": "1.0",
},
"paths": {
"/": {
"get": {
"x-amazon-apigateway-integration": {
"httpMethod": "POST",
"passthroughBehavior": "when_no_match",
"type": "aws_proxy",
"uri": `arn:aws:apigateway:us-west-2:lambda:path/2015-03-31/functions/${arn}/invocations`,
},
},
},
},
"x-amazon-apigateway-api-key-source": "HEADER",
"x-amazon-apigateway-binary-media-types": [ "*/*" ],
"x-amazon-apigateway-gateway-responses": {
"ACCESS_DENIED": {
"responseTemplates": {
"application/json": "{\"message\": \"404 Not found\" }",
},
"statusCode": 404,
},
"MISSING_AUTHENTICATION_TOKEN": {
"responseTemplates": {
"application/json": "{\"message\": \"404 Not found\" }",
},
"statusCode": 404,
},
},
})),
});
// Export the auto-generated AWS API Gateway base URL.
export const url = api.url;
boundless-analyst-51913
06/08/2021, 4:53 PMfailed to register new resource my-api-resource-name [aws:apigateway/stage:Stage]: Resource monitor is terminating
at Object.registerResource (/node_modules/@pulumi/pulumi/runtime/resource.js:219:27)
at new Resource (/node_modules/@pulumi/pulumi/resource.js:215:24)
at new CustomResource (/node_modules/@pulumi/pulumi/resource.js:307:9)
at new Stage (/node_modules/@pulumi/apigateway/stage.ts:200:9)
at new API (/node_modules/@pulumi/apigateway/api.ts:571:22)
at new HttpDeployment (/node_modules/@pulumi/api.ts:200:20)
at API.publish (/node_modules/@pulumi/api.ts:131:27)
at Resource.output (own code, line points to this codeWhen I run it again, it successfully creates that missing resource. I tried to debug it but I can't find out what the issue could be. Any hints on where to look or how to debug would be very appreciated.)return { url: api.publish().url };
brash-kite-78002
06/08/2021, 5:09 PMmysterious-belgium-44686
06/09/2021, 12:45 AMkafkaContainer = docker.Container("kafka-container",
image=kafkaImage.name,
restart="on-failure",
networks_advanced=[{ 'name': network.name }],
start=True,
envs=[
"KAFKA_BROKER_ID=1",
"KAFKA_ZOOKEEPER_CONNECT=zookeeper:2181",
"KAFKA_ADVERTISED_LISTENERS=<PLAINTEXT://kafka:29092>,PLAINTEXT_<HOST://localhost:9092>",
"KAFKA_LISTENER_SECURITY_PROTOCOL_MAP=PLAINTEXT:PLAINTEXT,PLAINTEXT_HOST:PLAINTEXT",
"KAFKA_INTER_BROKER_LISTENER_NAME=PLAINTEXT",
"KAFKA_OFFSETS_TOPIC_REPLICATION_FACTOR=1"
],
ports=[{
'internal': 9092,
}],
opts=pulumi.ResourceOptions(depends_on=[zkContainer])
)
topic = kafka.Topic("topic",
name="sample-topic",
replication_factor=1,
partitions=4,
opts=pulumi.ResourceOptions(depends_on=[kafkaContainer])
)
fresh-hospital-81544
06/09/2021, 1:38 AMcolossal-rainbow-39841
06/09/2021, 5:26 AMlemon-garage-82195
06/09/2021, 7:43 AMpulumi up
gives us the expect output, and the resources exist within Azure, however, we've noticed that running the pipeline again pulumi tries to delete a subnet even though there have been no changes made to the config of that subnet. Has anyone experienced a similar issue?quiet-laptop-25454
06/09/2021, 12:33 PMboundless-angle-56560
06/09/2021, 2:22 PMquiet-gold-81036
06/09/2021, 5:09 PMacceptable-army-69872
06/09/2021, 7:34 PMboundless-angle-56560
06/09/2021, 8:48 PMshy-architect-77550
06/09/2021, 11:11 PMfoobar = linode.NodeBalancer("foobar",
label="mynodebalancer",
region="us-east",
client_conn_throttle=20)
foofig = linode.NodeBalancerConfig("foofig",
nodebalancer_id=foobar.id,
port=8088,
protocol="http",
check="http",
check_path="/foo",
check_attempts=3,
check_timeout=30,
stickiness="http_cookie",
algorithm="source")
The error is: error: linode:index/nodeBalancerConfig:NodeBalancerConfig resource 'foofig' has a problem: Attribute must be a whole number, got 143111. Examine values at 'NodeBalancerConfig.NodebalancerId'.
orange-byte-86458
06/10/2021, 12:19 AMtf2pulumi
tool but, of course, nothing ever works on the first try 🙂
It seems like in our existing Terraform config we’re using https://registry.terraform.io/providers/gavinbunney/kubectl/latest provider for which there’s no direct Pulumi alternative and the tf2pulumi
tool fails with a no resource plugin 'kubectl'
error. My understanding was that I could use the --allow-missing-plugins
to make it proceed and then simply refactor the resulting code to use Pulumi’s native plugin but, unfortunately, --allow-missing-plugins
does nothing and tf2pulumi
still fails.
Is there an easy workaround for this or do I need to go the route of wrapping the kubectl
plugin via https://github.com/pulumi/pulumi-terraform-bridge, publishing it in the registry, etc., etc. ?
Thanks!gorgeous-minister-41131
06/10/2021, 1:51 AMgorgeous-minister-41131
06/10/2021, 1:52 AMhiera
for Pulumi configuration..gorgeous-minister-41131
06/10/2021, 1:54 AMgorgeous-minister-41131
06/10/2021, 1:55 AMgorgeous-minister-41131
06/10/2021, 1:55 AM