I know you can use extraIncludePaths to pull in additional files but you still need to define a callback closure

Just re-read the https://github.com/pulumi/docs/blob/master/reference/serializing-functions.md document, this helps and I think I can move forward there

For lambda env varibles, is it possible to enable the transit encryption option? I see we can supply a KMS ARN but that only covers it at rest

Is there an article to clearly define and explain the distinctions between the different available apis? And when to best use them? For example, I see there is a cloud api, an aws api, an awsx api, and the aws-serverless api.

message has been deleted

Does Pulumi perform a deep diff/compare of things like the

spec

property of a k8s Ingress resource? https://pulumi.io/reference/pkg/nodejs/@pulumi/kubernetes/extensions/v1beta1/#Ingress-spec I am finding that when updating the JSON of this field, which looks like

{ rules: ... }

, where the

...

changes, Pulumi is showing no changes.

i am new to AWS. i want to do as the title of this thread says... i want to assign a static IP address to a docker container or some other serverless solution. i have a ECS instance running on aws, this has a static IP assigned to it because i was able to find the option. this EC2 instance then runs a docker container with a caddy server to serve static content, and manage routing paths and subdomains. suppose i owned "helloworld.com"; i can create a subdomains like "test.helloworld.com" and route paths like "https://helloworld.com/hello/world" i would prefer not to need a ec2 instance running if i can figure out how to do this serverless-ly. as i mentioned previously, i am new to AWS and i think using pulumi.io exactly fits my requirements and seems to be easy to understand. ... but i cant figure out how to assign a static IP address to a container running on AWS. i'm new to AWS, so any guidance is appreciated.

I am setting up an API with `aws.apigateway.x.API()`:

const api = new aws.apigateway.x.API("name", {
	stageName: "demo",
    routes: [
	    {
	        path: "/",
	        method: "POST",
	        eventHandler: lambda,
	    },
	    {
	    	path: "/",
	    	method: "PUT",
	    	eventHandler: lambda,
	    }
    ]
});

and am attempting to attach an api key…

const api_key = new aws.apigateway.ApiKey("demo", {
	name: "demo",
	stageKeys: [{
		restApi: api.id,
		stageName: api.stageName
	}]
})

output from pulumi up is:

aws:apigateway:ApiKey (demo):
    warning: urn:pulumi:pulumi_demo::webserver::aws:apigateway/apiKey:ApiKey::demo verification warning: "stage_key": [DEPRECATED] Since the API Gateway usage plans feature was launched on August 11, 2016, usage plans are now required to associate an API key with an API stage
    error: aws:apigateway/apiKey:ApiKey resource 'demo' has a problem: "stage_key.0.stage_name": required field is not set
    error: aws:apigateway/apiKey:ApiKey resource 'demo' has a problem: "stage_key.0.rest_api_id": required field is not set

with api.ts, I am able to set stageName per

const stageName = args.stageName || "stage"; `

but apikey.ts doesn’t seem to ingest the var?

I was running a

pulumi destroy

... it listed a resource that was not created by my pulumi stack to be deleted. This resource was a prior existing resource that was added into the stack via an aws resource id. Will pulumi destroy this resource? If so, how do you tell pulumi to never destroy a resource not created by it? I got this resource via a

get

call.

const not_my_tbl = aws.dynamodb.Table.get('not_my_table', 'not_my_table')

*In general, is there a way to mark a resource to never be destroyed?

Is there a way to pass apigateway.Method arguments to apigateway.x.API()? I am having a hard time tracking

apiKeyRequired

and use of apigateway.Method at all (I have an apikey, usageplan, and usageplankey)

This code is causing

panic

Is there a good general design around functions that pass computed objects but then keep having URN naming collisions? Example is code where I feed in an array of service account emails from Service Account objects created earlier in the program.

keep getting [Object object] collisions

I created my first empty stack, but the web console shows "Bad Request: Stack still contains resources" when I attempt a delete. Even though I haven't touched anything on it. 🤔

In addition when I do a

pulumi new aws-javascript -s X

I get

error: no Pulumi project found in the current working directory

. Even though it says it do this in an empty directory (which it is).

Thanks for the help with the issues @bitter-oil-46081 and @white-balloon-205. I'm a long time Terraform and Serverless.js user, trying Pulumi out for the weekend as a replacement for some projects possibly.

May do a writeup on it 👍

Thanks for trying us out! Sorry you had a rough go of it, but we'll be here to help.

Just updated to the latest

gcp

and we are seeing

error: [500] Internal Server Error

I'm seeing the same for lots of operations, and can't access app.pulumi.com

Just pulumi preview on a previously working stack (with no component updates) gives me that error

Yes, some alarms on our end just went off and we are investigating.

We are seeing elevated error rates from our production service and are investigating. We'll share an update by 6:00 PST

We believe the issue is related to high CPU usage in our backend database and are failing over to a replica. We'll update again at 6:15 PST.

We believe the problem is solved, and will be monitoring all systems for subsequent issues.

Thank you for the quick response; things are working again for me

Is there a "best practices" document/writeup, or possibly a big example of a real world backend? I see the snippets of examples on Git, but have so many things in my mind... Primarily proper organization as the backend scales.

This is from the example code and it is running into an error

error: unexpected null property rrdatas[0]