Is it intentional that this provider binary continues to live / run when no pulumi CLI command is in the middle of executing;

pulumi-resource-azure-native.exe

?? I couldn't figure out why I couldn't rename a folder. Process Explorer found that this .exe was running and in the folder in question. I killed the process, and then I was able to rename the folder. Just wondering. Thanks.

Am I the only one that gets the error message truncated on my terminal when running a Pulumi up that fails?

Hi all, it looks like the

version

command of

3.26.0

is not returning a version number. Since updating to

3.26.0

, Homebrew thinks the version is

0.0.0

and keeps prompting for an update.

hi all. happy to be here. i'm trying to get crosswalk with ECS working but i can't quite get the port mappings right. i want two listeners on my ALB: 80 and 443, and I want 80 to redirect. got that part right. now i want 443 to be forwarded to a target group ON PORT 80 (not 443). however, i can't quite figure out how to do this without manually declaring the target group. it's currently forwarding everything to port 443 on the target group, which is not what i want. is this possible? code:

import * as pulumi from "@pulumi/pulumi";
import * as aws from "@pulumi/aws";
import * as awsx from "@pulumi/awsx";

// Create an ECS cluster explicitly, and give it a name tag.

const vpc = awsx.ec2.Vpc.getDefault();
const cluster = new awsx.ecs.Cluster("cluster", {
  vpc,
});

const zone = aws.route53.getZone({ name: "zone." });

// Create a load balancer on port 80 and spin up two instances of Nginx.
const lb = new awsx.lb.ApplicationLoadBalancer("alb");
const httpListener = lb.createListener("http", {
  port: 80,
  protocol: "HTTP",
  defaultAction: {
    type: "redirect",
    redirect: { protocol: "HTTPS", port: "443", statusCode: "HTTP_301" },
  },
});

const httpsListener = lb.createListener("https", {
  port: 443,
  protocol: "HTTPS",
  certificateArn,
});

const record = new aws.route53.Record("api-route", {
  zoneId: zone.then((zone) => zone.id),
  name,
  type: "A",
  aliases: [
    {
      name: lb.loadBalancer.dnsName,
      zoneId: lb.loadBalancer.zoneId,
      evaluateTargetHealth: false,
    },
  ],
});

const app = new awsx.ecs.FargateService("service", {
  cluster,
  taskDefinitionArgs: {
    containers: {
      nginx: {
        image: "nginx",
        portMappings: [httpsListener]
      },
    },
  },
  desiredCount: 2,
});

this makes all the requests go to the target group on port 443, but the target group is a service listening on port 80, so it 502s

What do you do in the case of a stuck update job? A fairly simple update of mine is stuck on deleting an AWS SG and has been for 14 minutes

hah it just timed out as I said that

Hi! I still have not found a solution to this problem. Is there anyone who can shed some light on a possible workaround? I am using pulumi azure classic. Have a good day!

Hi, from my understanding

kubernetes.helm.v3.Release

does the same API calls as

helm

. So my expectation is that, after a pulumi deployment, I should be able to list the helm deployments with

helm list

. Am I wrong? Thanks

Great video on the bit.ly dynamic provider @quiet-wolf-18467 🎉

Thanks, @wonderful-twilight-70958 😄

just out of curiousity, how do I export Swagger JSON from my APIGatewayV2 objects in Python?

How can one ensure that the

[org]/prod

stack for a project never gets deleted (or has some relatively difficult guard against it)?

Hi again! I got a strange issue when doing a "pulumi refresh" against AWS. It looks like the source in a BucketObject is replaced with a absolute reference to a pulumi temp-file on my local computer, see attached image. It looks very similar to this issue: https://github.com/pulumi/pulumi-aws/issues/1521 ...but it persists for me even after updating to the latest Pulumi packages with Yarn. I read in some other threads linked via that issue hints that this might be because we are doing something unexpected, but it is a bit too technical for me. Any help would be appreciated since I assume this is not how it should work? Update: Using TypeScript

Hi. I'm trying to setup error actions for IoT topic rules, the Pulumi console shows me that everything was successfully updated, But when I go to IoT Rule detail I do not see the error action configured, ¿any idea?, sample code below

export const iotRule = new aws.iot.TopicRule("sampleRule", {
    enabled: true,
    sqlVersion: "2016-03-23",
    sql: config.require("query"),
    kinesis: {
        streamName: stream.name,
        roleArn: role.arn,
        partitionKey: '${partitionKey}'
    },
    errorAction: {
        republish: {
            topic: 'stage/iot/errors',
            roleArn: iotErrorRole.arn,
        }
    },
})

I just saw https://pulumi-community.slack.com/archives/C84L4E3N1/p1635911681308500?thread_ts=1635911465.307800&cid=C84L4E3N1 So, just to be clear, if I see a Python example online which has

import pulumi_docker as docker

I need to follow both below two steps? Step One:

pulumi plugin install package docker 3.1.0

Step Two:

source venv/bin/activate
pip install pulumi_docker

It's not clear from Lee's message how the automatic thing can happen for Node/Python. He points to a Go script which I can't interpret.

Anybody facing this issue https://github.com/pulumi/pulumi-kubernetes/issues/1925

Any folks having a similar problem with the Fastly provider? https://github.com/pulumi/pulumi-fastly/issues/119

Is something up with the cloudflare provider? After working for over a year, i suddenly get the following (3.26.1 + 4.4.0 cloudflare)

Diagnostics:
  cloudflare:index:Record (staging-upload-1-1cd4):
    error: could not validate provider configuration: 1 error occurred:
    	* invalid value for api_key (API key must only contain characters 0-9 and a-f (all lowercased))

The config is set in the automation api with these values:

'cloudflare:accountId': {
    value: config.cloudflareAccountId,
  },
  'cloudflare:apiKey': {
    value: config.cloudflareApiKey,
    secret: true,
  },
  'cloudflare:email': {
    value: config.cloudflareEmail,
  },

and config.cloudflareApiKey contains the correct key.

Hi Everyone, I have opened the ticket for pulumi-fastly https://github.com/pulumi/pulumi-fastly/issues/159. I am getting an error when trying to add logging for Fastly service. Would appreciate any help or ideas. Thank you

I’m a bit confused by this AWS “getter”:

// GetOpenIdConnectProvider gets an existing OpenIdConnectProvider resource's state with the given name, ID, and optional
// state properties that are used to uniquely qualify the lookup (nil if not required).
func GetOpenIdConnectProvider(ctx *pulumi.Context,
	name string, id pulumi.IDInput, state *OpenIdConnectProviderState, opts ...pulumi.ResourceOption) (*OpenIdConnectProvider, error) {
	var resource OpenIdConnectProvider
	err := ctx.ReadResource("aws:iam/openIdConnectProvider:OpenIdConnectProvider", name, id, state, &resource, opts...)
	if err != nil {
		return nil, err
	}
	return &resource, nil
}

If feels like the

state

argument is redundant… since this function requires the resource

id

which I’m assuming this would make this unique. What’s the point of the

state

arg?

this is not specific to

Go

(even though I’m presenting this question from the Go provider)

Hey all, I exported my resource group (and its resources) in one ARM file, but when I try to convert it, only the resource group is being converted (for typescript), and for Go, I get an error. Is there a better way to import an existing setup to be managed?

does Pulumi have neovim lsp-config support ?

or can only use in vscode and such

Any idea why a user who we’ve confirmed is logged in (via

pulumi login

) is getting this error:

could not decrypt configuration value: [400] Message authentication failed

When they run

pulumi config --show-secrets

? Update: I am also getting the same error on my end and I’m an admin for our team. Steps to reproduce: 1.

pulumi stack select ORG/prod

2.

pulumi config --show-secrets

Hi dear community, May I ask a question? I'm quite new to Pulumi, so I apologise if it might seem silly. I use

pulumi.export()

to export a variable in

file1.py

. I'm going to use this variable in

file2.py

Is there any way to get this variable in

file2.py

? So far I have found how to import this variable in CLI only

Hello, anyone knows a good way to implement this?

import * as aws from '@pulumi/aws'
import * as pulumi from '@pulumi/pulumi'

const failuresBackupBucketName = pulumi.output(
    aws.ssm.getParameter({ name: "/s3/bucket/failuresBackup" })
)

export const failuresBackupBucket = aws.s3.getBucket({
    bucket: failuresBackupBucketName.value
})

Im getting the following error