Are there any examples for python and ecs using

TaskDefinition

and

Service

? all the examples I can find are for JS using @aws-infra, which seems like a shortcut. Specifically creating a ecs service, the

network_configuration

part of the documention is not clear.

Is it possible to merge or apply multiple config files? e.g.: We have some shared config in

Pulumi.review.yaml

and some extra config in

./.deployment/Pulumi.extra.yaml

. Is that possible? This is related to the use case I described earlier of having arbitrarily many stacks (stack-per-branch). When creating what GitLab calls review apps, we may, for example, generate random credentials to inject as secrets per-stack, but we would also have a bunch of static config stored in a shared file.

When creating a

new eks.Cluster

how can I specify the tags to set on all the EC2 hosts, ASG, launch config, etc.?

My article is now published at FreeCodeCamp medium publication: https://medium.freecodecamp.org/from-yaml-to-typescript-a-developers-view-on-cloud-automation-bba5365439f4

Are we able to self host stacks? Or is this paid for software.

Hi community, I just came across Pulumi some days ago... looks really really cool 🙂 I started to used tf2pulumi to convert some of my terraform infrastructures. Is there a list of supported providers? What can I do to add more providers ? e.g.

* provider.huaweicloud: version = "~> 1.3"
* provider.mysql: version = "~> 1.5"
* provider.tls: version = "~> 1.2"* 
* provider.kubernetes : version = custom fork

Hi everyone, I’m new to pulumi but looking forward to using it. I was wondering if any one has information about partnerships with pulumi?

Is there a way to tell pulumi to update a kubernetes resource if it already exists, instead of failing with

error: Plan apply failed: some_resource_here already exists

?

Use case: add a few rules to already existing

system:heapster

ClusterRole. Workaround: remove the role before running

pulumi up

.

Getting this exception with a

awsx.ecs.FargateService

.

aws:ecs:TaskDefinition (http-backend):
    error: Plan apply failed: ClientException: The sum of all container 'cpu' values cannot be greater than the value of the task 'cpu'.
        status code: 400, request id: bff208c6-3c49-11e9-a829-c73da6c6ad94

I have one container with cpu 1024 and memory 2048 and another with cpu 256 memory 512. Both of those are valid Fargate task definitions: https://docs.aws.amazon.com/AmazonECS/latest/developerguide/task-cpu-memory-error.html

While I made it work using a workaround, I would still appreciate an answer, for all the future occurrences. 🙂

What troubleshooting steps should I do if a

preview

,

up

just hang? I was making changes and backed them all out and still hangs? Tried

-v 5

but didn't see any additional logging

this is on Mac OS latest, using JS - was working fine earlier today and yesterday

Has anyone used the

baseUrl

option with Pulumi in typescript? https://www.typescriptlang.org/docs/handbook/module-resolution.html I am finding that I can compile manually with

tsc

fine, but when running the

pulumi

CLI, modules depending on resolution from

baseUrl

cause errors.

Which language, supported by Pulumi, is the most feature-complete at the current time? JS, Go or Python

or others

i just started looking into Pulumi yesterday, and was not productive at all in Python - JS seems the way to go - it has the most examples, documentation

Somebody just sent me a link to Pulumi, looks very good, like terrafrom but without horrible DSL that does not do what you want. However it appears that app.pulumi.com is not open source, and "it is possible to use Pulumi without the service, which works a lot more like Terraform, but it is harder to do and opt-in", so basically this is a vendor lock in, right? No option to run a version of app.pulumi.com locally without getting inferior results?

Possibly a stupid question, but how to I get the

repositoryUrl

of a ECR repo as a string so I can update my task definition (which takes

containerDefinitions

as a string)?

My

pulumi preview

has become incredibly slow as soon as a

k8s.yaml.ConfigFile

resource is instantiated. Comment it out: quick. Uncomment: slow. I have been using lots of these, and only just recently encountered this issue. They did not previously cause any slowness. Any ideas what could have changed or be causing this?

I just did a

pulumi destroy

and everything appears to have deleted but I got this message:

Diagnostics:
  pulumi:pulumi:Stack (infra-dev):
    E0301 17:38:17.968812   54963 streamwatcher.go:109] Unable to decode an event from the watch stream: http2: server sent GOAWAY and closed the connection; LastStreamID=85, ErrCode=NO_ERROR, debug=""
    E0301 17:38:17.968812   54963 streamwatcher.go:109] Unable to decode an event from the watch stream: http2: server sent GOAWAY and closed the connection; LastStreamID=85, ErrCode=NO_ERROR, debug=""
    E0301 17:38:17.968814   54963 streamwatcher.go:109] Unable to decode an event from the watch stream: http2: server sent GOAWAY and closed the connection; LastStreamID=85, ErrCode=NO_ERROR, debug=""
    E0301 17:38:17.968814   54963 streamwatcher.go:109] Unable to decode an event from the watch stream: http2: server sent GOAWAY and closed the connection; LastStreamID=85, ErrCode=NO_ERROR, debug=""

Hi, does anyone have advice on how to configure ingress with HTTPS when using kubernetes? i have previously used caddy to set this up because it has the ability to automatically fetch and update TLS certs. i can see in the documentation when creating a container app, you can specify a path to the

Dockerfile

with

awsx.ecs.Image.fromPath

as show in the example on https://pulumi.io/quickstart/aws/tutorial-service.html... i would like something similar so i can build an image for kubernetes to work on an example like shown at: https://github.com/pulumi/examples/tree/master/kubernetes-ts-exposed-deployment. how i am trying to create a caddy server:

image: awsx.ecs.Image.fromPath("caddy", {dockerfile: "./src" }),

unlike in the example on the pulumi tutorial, it seems

fromPath

in the latest version (0.16.5) requires 2 parameters. but i cant figure out how the second parameter needs to be specified. i have tried searching the documentation but i am unable to find what i am looking for. perhaps i am searching in the wrong place?

Is it possible to use the output hostname from an AWSX NLB definition as an environment variable in a Fargate service? The service is a proxy which needs to send traffic to an internal NLB

I feel like I’ve asked this before, but is it possible to reference stack outputs from within another stack?

got this error after trying to redeploy kubernetes; not sure why kubeconfig yaml has broken even though changes have not been made to the code... or how to figure out what is breaking it.

+  pulumi:providers:kubernetes kubeconfig create 
    kubernetes:core:Secret docker-secret-1a  error: failed to parse kubeconfig: yaml: line 12: could not find expected ':'
    kubernetes:core:Secret docker-secret-1a  1 error
 
Diagnostics:
  kubernetes:core:Secret (docker-secret-1a):
    error: failed to parse kubeconfig: yaml: line 12: could not find expected ':'

hello, having some issues with creating a stack in kubernetes with a helm chart stable/prometheus-operator. It is giving me a duplicate resource URN error, I have manually searched for a duplicate on the cluster (doesn’t exist), tried a different namespace, tried a different stack name. Looking for some guidance where to look

Diagnostics:
  kubernetes:<http://rbac.authorization.k8s.io:Role|rbac.authorization.k8s.io:Role> (default/prometheus-operator-prometheus):
    error: Duplicate resource URN 'urn:pulumi:prometheus-monitoring-test::eks-devops-metrics-server::kubernetes:<http://helm.sh/v2:Chart$kubernetes:rbac.authorization.k8s.io/v1:Role::default/prometheus-operator-prometheus';|helm.sh/v2:Chart$kubernetes:rbac.authorization.k8s.io/v1:Role::default/prometheus-operator-prometheus';> try giving it a unique name

hi, we have a big stack with a lot of stuff(networking, eks, mysql, elasticsearch, redis etc...) and we want to separate it to microstacks, is it possible to do this without redeploying? One way to export and hack the state files, but that's the last resort, are there any better way to move resources between stacks?

Is there a way to molly guard some Pulumi resources? e.g.: I want to make sure that a comment in the wrong place doesn't cause

pulumi up

to destroy a persistent volume in my CI/CD scripts. (Molly guard from the jargon file: http://www.catb.org/jargon/html/M/molly-guard.html)

Any good practices for rolling back a fargate service release?