Reading through how AWS recommends deploying databases to EC2 it seems that the standard is: • Deploy a given quorum to each AZ in a set of AZs • When upgrading, take instances down one at a time (or at least one at a time per quorum), spin up the replacement, and then attach the network interface from the terminated instance to the newly created instance. How would one implement this in Pulumi? It seems like you'd want to ensure that, across deployments, you choose the AZs deterministically, and that you don't destroy network interfaces as you transition from one EC2 instance to another. I also am curious if I can specify that, for a given quorum, we only take down a node when all other nodes are ready? Or perhaps this is asking the wrong things from Pulumi, and I should be taking another approach?

Howdy folks! Super stoked to be trying out pulumi with python

Hi everyone, is there a way to clean up your pulumi organization. We have a microservice setup and have been on a learning curve with pulumi to obtain our end goal and have a lot of mess in our pulumi account do to trial and error plus internal restrictions. This is just one project and we have 10+ Thought that I could create a new organization and then transition to that so that we start from scratch. But as far as i see only one organization is allowed? Seems like an enormous work if we have to destroy and remove all stacks on all projects most of them are deleted in azure with az group delete on the resource group… Thanx in advance

Hi all, we are trying to use Pulumi Kubernetes Operator to enable commit SHA based deployments in our AKS clusters. It seems to work all fine when we do commit and trigger the deployments based on that on local environment. However, this doesn't work in CI/CD environments as we are committing the same environment repo with aggressive git PRs/CI builds and the same stack file is being updated with the next container image version which leads to conflict issues. Is there a way to get around this issue or get rid if this approach altogether? Is there a way to watch for published images in container registry and then trigger deployments/image version change as in other gitops tools like FluxCD, ArgoCD, etc? Any help would be much appreciated.

Hello guys ! I have been created a Dynamic Provisioner. ! But now, all my unit tests are broker, Do you know now to Mock my Dynamic Provisioner ?

Hi everyone, I have a query apigatewayV2 can you use the region us-east-1?

I am running a project with apigatewayV2 and region us-east-2 and it works fine for me. But when I try to do it with the us-east-1 region it gives me an error

Is there a way to disable the default providers (e.g. for AWS/Kubernetes), to force you to always have to specify a provider? I am always worried I will forget setting the provider somewhere and it will use the default ones with whatever they are configured

is there a way to register service instance for cloud map service in aws?

Hi everyone, How to destroy a specific resource in Pulumi without disturbing other resources.

anyone else getting errors with pulumi's api?

Hi everyone Can we use the AWS API Gateway V2 HTTP API arrogantly? I can't find an example :(. But if I found one in apiGateway:

import * 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;

Hi, I have a inline program that creates a Table and an API resource from pulumi-cloud, and when I run it the first time (creating the resources) I get this error:

failed 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 code

return { url: api.publish().url };

)

When 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.

Hello Everyone! Is there any way to change a Helm chart values after it's got defined in the code? I need to deploy the Cilium chart, but I can't deploy it with ServiceMonitors and Ingress because of dependencies that are deployed later on. Thus, I'm trying to find a way to change the chart after all my dependencies are installed.

I'm trying to use Pulumi to manage some docker containers. One container is running Kafka. How can I have Pulumi wait until Kafka is up and running before creating the topic?

kafkaContainer = 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])
    )

hi. my internet just cut out during pulumi up and now my stack cant be found. How to recover?

can i output json during pulumi up ? similar to pulumi preview --json ?

Morning guys, We're experiencing an odd issue after migrating from azure-nextgen to azure-native. A

pulumi 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?

Hello! has anyone encountered this issue when using pulumi automation api on a CI/CD pipeline? If someone could help me on this I'd be glad to offer sweet treats and advices!

Hi, perhaps a silly question but is it possible to auto-generate terraform files from pulumi ? Does anybody know some tool ?

hi all, I’m looking for a freelance Pulumi consultant for a number of projects on our AWS infra. is there a directory/certification plan by Pulumi?

SaaS company gave me a cloud formation template instead of clear instructions on what they want for permissions. I see a couple options getting this into pulumi; reverse engineer what's in the cf template, which I'll probably screw up, or use the template, then import the resources into pulumi. Anyone else have any bright ideas? There's not some cf to pulumi magic someone wrote is there?

Hi, is there a way how to work with a hierarchy of docker images ? I mean - to create base docker image and child image derived from the base one, all in single pulumi run ?

Hi - I followed the example for creating a linode nodebalancer per the docs (literally cut and paste the example) and pulumi returns an error. The example is this snippet from https://www.pulumi.com/docs/reference/pkg/linode/nodebalancerconfig/:

foobar = 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'.

Hi, all! I’m checking out Pulumi as a potential Terraform replacement for our project. I was quite excited about the

tf2pulumi

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!

Is there a way yet, in pulumi, to have project-wide configurations vs just stack? without implementing a custom system, copy-pasta is rampant in a lot of our projects unless I use custom map mergers, and do all of the configuration logic in code… which defeats the purpose of even using pulumi’s config system outside of secrets.

I yearn for the days of something like

hiera

for Pulumi configuration..