Not sure if this is the right place to ask or not but anyways, is it a good idea to deploy a database using containers like fargate or ECS or is it better to use EC2 instead?

Any idea what to do when this happens? We got the first error, and then when running up again, we got the second.

~   └─ gcp:container:Cluster         gke                     updated     [diff: ~addonsConfig]
panic: fatal: An assertion has failed

goroutine 535 [running]:
<http://github.com/pulumi/pulumi/pkg/util/contract.failfast(...)|github.com/pulumi/pulumi/pkg/util/contract.failfast(...)>
	/private/tmp/pulumi-20190604-14204-2zvez6/src/github.com/pulumi/pulumi/pkg/util/contract/failfast.go:23
<http://github.com/pulumi/pulumi/pkg/util/contract.Assert(...)|github.com/pulumi/pulumi/pkg/util/contract.Assert(...)>
	/private/tmp/pulumi-20190604-14204-2zvez6/src/github.com/pulumi/pulumi/pkg/util/contract/assert.go:26
<http://github.com/pulumi/pulumi/pkg/backend.(*sameSnapshotMutation).mustWrite(0xc000010470|github.com/pulumi/pulumi/pkg/backend.(*sameSnapshotMutation).mustWrite(0xc000010470>, 0xc000a6a9a0, 0xc0006607e0, 0xc0003e1f60)
	/private/tmp/pulumi-20190604-14204-2zvez6/src/github.com/pulumi/pulumi/pkg/backend/snapshot.go:192 +0x3f4
<http://github.com/pulumi/pulumi/pkg/backend.(*sameSnapshotMutation).End.func1(0xc0003e1f60)|github.com/pulumi/pulumi/pkg/backend.(*sameSnapshotMutation).End.func1(0xc0003e1f60)>
	/private/tmp/pulumi-20190604-14204-2zvez6/src/github.com/pulumi/pulumi/pkg/backend/snapshot.go:237 +0xd0
<http://github.com/pulumi/pulumi/pkg/backend.NewSnapshotManager.func1(0xc0019f18c0|github.com/pulumi/pulumi/pkg/backend.NewSnapshotManager.func1(0xc0019f18c0>, 0xc001a21600, 0xc0019f1920, 0xc0019f1980)
	/private/tmp/pulumi-20190604-14204-2zvez6/src/github.com/pulumi/pulumi/pkg/backend/snapshot.go:564 +0x108
created by <http://github.com/pulumi/pulumi/pkg/backend.NewSnapshotManager|github.com/pulumi/pulumi/pkg/backend.NewSnapshotManager>
	/private/tmp/pulumi-20190604-14204-2zvez6/src/github.com/pulumi/pulumi/pkg/backend/snapshot.go:554 +0x150

error: [409] Conflict: Another update is currently in progress.

Can

pulumi.StackReference

refer to a state stored in an S3 bucket?

i have a question about the new relic package. I see that this was resolved https://github.com/pulumi/pulumi-newrelic/issues/1. but I dont think it resolved the issue. code sample in thread

anyone have a sane way (typescript) to get an actual

string

(or a list of strings) out of

aws.ec2.getSubnetIds

? I just want the subnet IDs. everything I've tried results in various types that are variously incompatible. can't even get something I can simply

export

without blowing up the world. a simple

export const subnetIds =  aws.ec2.getSubnetIds({ vpcId: vpcId, });

results in

error TS1184: Modifiers cannot appear here.

trying to anything else tends to result in

error TS2740: Type 'Promise<GetSubnetIdsResult>' is missing the following properties from type 'Input<string>[]': length, pop, push, concat, and 26 more.

I got this error trying to add a subnet to my ES -->

You must specify exactly two subnets because you've set zone count to two

, i was thinking that will have been fix since 2 months.

I added a

livenessProbe

to my

Deployment

and then removed it and received this exception:

TSError: ⨯ Unable to compile TypeScript:
    src/index.ts(418,21): error TS2345: Argument of type '{ metadata: { namespace: Output<string>; name: string; labels: { "<http://app.kubernetes.io/name|app.kubernetes.io/name>": string; "<http://app.kubernetes.io/instance|app.kubernetes.io/instance>": string; "<http://app.kubernetes.io/version|app.kubernetes.io/version>": string; }; }; spec: { selector: { ...; }; replicas: number; template: { ...; }; }; }' is not assignable to parameter of type 'Deployment'.
      Types of property 'spec' are incompatible.
        Types of property 'template' are incompatible.
          Types of property 'spec' are incompatible.
            Type '{ replicas: number; containers: { name: string; image: string; env: ({ name: string; value: Output<string>; } | { name: string; value: string; } | { name: string; valueFrom: { fieldRef: { fieldPath: string; }; }; })[]; resources: { ...; }; }[]; }' is not assignable to type 'PodSpec | Promise<PodSpec> | OutputInstance<PodSpec> | undefined'.
              Object literal may only specify known properties, and 'replicas' does not exist in type 'Input<PodSpec>'.
    
        at createTSError (/home/kenny/compute_software/infrastructure/pulumi-k8s-src/node_modules/ts-node/src/index.ts:261:12)
        at getOutput (/home/kenny/compute_software/infrastructure/pulumi-k8s-src/node_modules/ts-node/src/index.ts:367:40)
        at Object.compile (/home/kenny/compute_software/infrastructure/pulumi-k8s-src/node_modules/ts-node/src/index.ts:558:11)
        at Module.m._compile (/home/kenny/compute_software/infrastructure/pulumi-k8s-src/node_modules/ts-node/src/index.ts:439:43)
        at Module._extensions..js (module.js:664:10)
        at Object.require.extensions.(anonymous function) [as .ts] (/home/kenny/compute_software/infrastructure/pulumi-k8s-src/node_modules/ts-node/src/index.ts:442:12)
        at Module.load (module.js:566:32)
        at tryModuleLoad (module.js:506:12)
        at Function.Module._load (module.js:498:3)
        at Module.require (module.js:597:17)

It is not clear what this means. Is this expected?

Is there a pulumi provider for gitlab? I'd like to automate creation of pipeline schedules in a gitlab project as per: https://docs.gitlab.com/ee/api/pipeline_schedules.html#create-a-new-pipeline-schedule

Hello people, When creating a new stack, is there a way to be non-interactive (for the

Enter your passphrase to protect config/secrets:

) the option

--non-interactive

does not seems to have an effect on it.

or maybe there is a way to disable the secret management ?

If I change the

identifier

of a

aws.rds.Instance

, Pulumi thinks it needs to replace the instance. This property is actually able to be changed in place.

I am trying to create a new stack. After running

pulumi up

, I receive this message in the preview.

error: Running program '/home/kenny/compute_software/infrastructure/pulumi-k8s-src' failed with an unhandled exception:
    Error: invocation of aws:ec2/getSubnet:getSubnet returned an error: invoking aws:ec2/getSubnet:getSubnet: multiple subnets matched; use additional constraints to reduce matches to a single subnet
        at monitor.invoke (/home/kenny/compute_software/infrastructure/pulumi-k8s-src/node_modules/@pulumi/pulumi/runtime/invoke.js:74:33)
        at Object.onReceiveStatus (/home/kenny/compute_software/infrastructure/pulumi-k8s-src/node_modules/grpc/src/client_interceptors.js:1205:9)
        at InterceptingListener._callNext (/home/kenny/compute_software/infrastructure/pulumi-k8s-src/node_modules/grpc/src/client_interceptors.js:568:42)
        at InterceptingListener.onReceiveStatus (/home/kenny/compute_software/infrastructure/pulumi-k8s-src/node_modules/grpc/src/client_interceptors.js:618:8)
        at callback (/home/kenny/compute_software/infrastructure/pulumi-k8s-src/node_modules/grpc/src/client_interceptors.js:845:24)

I've never received an exception during the preview. None of those lines in the stack trace are pointing to my code. Any idea what could cause this?

pulumi up

fails if a deployment is scaled to 0, because it is marked unhealthy

* Minimum number of Pods to consider the application live was not attained

anyone out there using s3 state and want to discuss workflows around multiple accounts? (ie, dev stack on dev account, stage stack on stage account, prod on prod account - as a simplified example) since each account has to have it's own state bucket, and bucket names are globally unique, this seems....painful. I cant just

config:aws:profile

in each stack, it seems like I have to wrapper the whole process to determine a bucket name for the stack and do a login.....

I’m going to need to blue/green at least my nginx deployment on k8s. We haven’t had a problem with anything else using rolling updates (Deployment/Service/Ingress) but recently found that cloudflare cached a 404 for a file that hit an old replica - so site went non functional. Any recommendations on discretely standing up new nginx replicas and cutting over?

Is there a pulumi property that would tell me if my current stack has had a successful update before?

Is it possible to maintain state about a

ComponentResource

?

When creating a

pulumi.dynamic.Resource

, how unique does the

id

returned from the

create

method have to be? Should it look like the Pulumi urn strings (i.e.

urn:pulumi:prod::vm-scaler::pulumi:pulumi:Stack::vm-scaler-prod

)?

My dynamic resource is showing up as

pulumi-nodejs:dynamic:Resource                       ions

in the

pulumi up

preview. Is there a way to change that?

In the

create

method of my

pulumi.dynamic.ResourceProvider

, I have some Pulumi `Output`s that I want to wait for before marking my resource as created. How would I wait for the Outputs to materialize?

Hello guys, i am working with pulumi using JavaScript and AWS, i want to create a CloudWatch Dashboard and i need to specify a dashboarbody that is a JSON, i want to create a dashboard to monitoring the CPU of my auto scaling group, and i must to specify the name of auto scaling but when i get the name of the ASG already created pulumi return me a promise.

OutputImpl { __pulumiOutput: true, isKnown: Promise { <pending> }, isSecret: Promise { <pending> }, resources: [Function], promise: [Function], toString: [Function], toJSON: [Function], apply: [Function], get: [Function] }

i don't know how capture the specify name of my auto scaling, in the documentation say that i can use apply but the response is the same

i use the constructor ASG_Creation = new aws.autoscaling.Group(parameters....) and mapping the name of ASG using ASG_Creation.name but when i pass this value of the json i get the error.

Totally low priority thing: Am trying out the github actions: • I added the example file at

.github/main.workflow

• I added my secrets to github’s secrets • I added those secrets to the secret arrays in

main.workflow

However it’s error-ing out on commit:

> protobufjs@6.8.8 postinstall /github/workspace/node_modules/protobufjs
[resource plugin kubernetes-0.24.0] installing
npm WARN aws-typescript@ No description
npm WARN aws-typescript@ No repository field.
> node scripts/postinstall

added 202 packages from 243 contributors and audited 1115 packages in 21.869s
npm WARN aws-typescript@ No license field.

found 0 vulnerabilities

### FAILED Pulumi Preview (Merged Stack) 23:28:50Z (1m54.161s)

Everything above this code snippet is all success. Any thoughts?

Calling [toJSON] on an [Output<T>] is not supported. To get the value of an Output as a JSON value or JSON string consider either: 1: o.apply(v => v.toJSON()) 2: o.apply(v => JSON.stringify(v)) See https://pulumi.io/help/outputs for more details. This function may throw in a future version of @pulumi/pulumi.

Can an output of a

pulumi.dynamic.Resource

be a function?

Every time I change my

pulumi.dynamic.Resource

, I get this diff message

[diff: ~__provider]

. What does this mean?

Is there a community library or something for making the writing of AWS IAM policies a little more type-safe?