Hello, is anyone able to successfully manage aws wafv2 resources (classic|native) with Pulumi? I'm experiencing breaking issues with both providers.

What would be the proper way to write this without hackily discarding the

apply

return value in

recordsets.apply

?

const recordsets = privateEndpoint.customDnsConfigs.apply(x => {
  if (typeof x === 'undefined') {
      return [];
  }

  const result = [];
  for (const dnsConfig of x) {
      const name = dnsConfig.fqdn!.split('.')[0];
      const ipAddresses = dnsConfig.ipAddresses!.map(x => {
          return {ipv4Address: x};
      });

      result.push({
          name: name,
          ipAddresses: ipAddresses
      });
  }

  return result;
});

recordsets.apply(rs => {
  for (const x of rs) {
      new network.PrivateRecordSet(`resource-pe-dns-${name}`, {
          privateZoneName: zone.name,
          recordType: "A",
          relativeRecordSetName: x.name,
          resourceGroupName: resourceGroup,
          ttl: 300,
          aRecords: x.ipAddresses
      });
  }

  return true;
});

Hi! Is there a way to rename a project?

It appears the Fargate TS sample code (link) uses deprecated bindings. It uses

awsx.elasticloadbalancingv2.NetworkListener

, but this no longer exists. I think it moved from

awsx

to

aws

at some point, to

aws.elasticloadbalancingv2.Listener

. (Could someone verify / explain what falls under

awsx

vs

aws

?) And then I find out from the docs that now this is deprecated in favor of

aws.lb.Listener

, so I should really be using that? And to further the confusion, I learn that everything under

@pulumi/aws

is known as classic, and if I want to stay modern I should actually be using

@pulumi/aws-native

instead of any of the options above? Incredibly, although

elasticloadbalancingv2

got renamed to

lb

in classic, it's back to being called

elasticloadbalancingv2

in native!

Is there a set of default and defined policies that we can run against our deployment on a regular basis ? Right now i am trying to figure out compliance related issues with my existing pulumi stack, and going forward, I would like to encode those into pulumi polices or opa policies. Any recommendations on this use case.

Hello there! Just trying out to write a custom resource. How do I access a provider (e.g. postgresql) to get access to the hostname of the db cluster?

Does anyone know how to force pulumi to reinstall plugin binary for the aws provider using the right architecture? I'm on an m1 mac, and for some reason the plugin binary is using amd64 instead of arm.

I am using pulumi with c# and I want to run some c# code ONLY if specific resource is created. how do I do it ?

Hey guys A question on upgrading

confluentcloud

provider from

0.1.0

to

1.x

pulumi up

operation with

refresh

flag throws error below and I tried the approach suggested in this [thread](https://github.com/pulumi/pulumi-confluentcloud/pull/14) but unfortunately it didn’t work either as running

refresh

gave me the same error.

panic: interface conversion: interface {} is nil, not string

Another method I’ve tired without

refresh

while it didn’t emit the error, it wanted to replace the kafka topic which we cannot do as doing so would cause data loss in our prod environment. So I am looking for the right way to upgrade the package.

Hi， Why is there an error ? as a different region for the bucket?

aws:s3:Bucket (S3-IoT-stage-job-jar):
    error: deleting urn:pulumi:stage-import-clone::stage_only::aws:s3/bucket:Bucket::S3-IoT-stage-job-jar: 1 error occurred:
        * error deleting S3 Bucket (s3-iot-stage-job-jar-7e2c66a): IllegalLocationConstraintException: The ap-east-1 location constraint is incompatible for the region specific endpoint this request was sent to.
        status code: 400, request id: PP0EY31SN0BDDB95, host id: 3Ssyi806zke54MGOBFSsvK3pAh11K3QQi6eQZPulDsBUnAeR5rigSvGkVen91PNduIU3QPgcXJY=
 
  aws:s3:Bucket (S3-IoT-stage-onecloud-customer-files):
    error: deleting urn:pulumi:stage-import-clone::stage_only::aws:s3/bucket:Bucket::S3-IoT-stage-onecloud-customer-files: 1 error occurred:
        * error deleting S3 Bucket (s3-iot-stage-onecloud-customer-files-46fb81f): IllegalLocationConstraintException: The ap-east-1 location constraint is incompatible for the region specific endpoint this request was sent to.
        status code: 400, request id: PP03BQD656QWS92Z, host id: nbOU5sqTDuOe0KhiwElXHBpg942got9OavgN0ASR7MbMQp8MbhUcjpoE3oSpeeYmZJNhxfyz5HQ=

But I create it by the same code.

Hey, is there a way to force a recreate on a resource if another resource was updated? For example, if resource

X

is updated I always want resource

Y

to update as well (but not the inverse). I've tried to use

depends_on

but it doesn't make a difference

Hi here, is there a way to easily update golang runtime to 1.19.3+ in pulumi to resolve vulnerabilities issues.

Hi, I am trying to deploy a VPC with

pulumi-awsx

to a newly created account using `assume_role`:

import pulumi
import pulumi_aws as aws
import pulumi_awsx as awsx

config: dict = {
    "skip_credentials_validation": True,
    "skip_metadata_api_check": False,
}

org_provider = aws.Provider("org-provider", **config)

account = aws.organizations.Account(
    "account", email="<mailto:test@example.com|test@example.com>", role_name="account-role", opts=pulumi.ResourceOptions(provider=org_provider)
)

provider = aws.Provider(
    "account-provider",
    assume_role=aws.ProviderAssumeRoleArgs(
        role_arn=pulumi.Output.concat("arn:aws:iam::", account.id, ":role/", account.role_name)
    ),
    **config
)

vpc = awsx.ec2.Vpc("vpc", opts=pulumi.ResourceOptions(provider=provider))

This throws an error on

pulumi preview

already:

Exception: Cannot read properties of undefined (reading 'length')
    error: TypeError: Cannot read properties of undefined (reading 'length')
        at Vpc.getDefaultAzs (/snapshot/awsx/bin/ec2/vpc.js:184:26)
        at processTicksAndRejections (node:internal/process/task_queues:96:5)
        at Vpc.initialize (/snapshot/awsx/bin/ec2/vpc.js:45:103)

My dependencies are:

pulumi==3.48.0
pulumi-aws==5.23.0
pulumi-awsx==1.0.0

When I comment out

assume_role

it works. It looks like it cannot resolve tha availability zones. When I add

availability_zone_names=["eu-central-1a", "eu-central-1b"]

to

awsx.ec2.Vpc

explicitly, it works as well. Is that intended behaviour? Am I missing something?

Is there way to activate an existing workflow (that is triggered by workflow_dispatch) for repository, from Pulumi ? I have the Github token for GitHub API

A few of us have noticed this with Python programs lately — wanted to share this here in case anyone else is seeing it too: https://pulumi-community.slack.com/archives/CDE799L1M/p1670513358998609

I'm using pulumi to write snowflake infrastructure. I originally imported many snowflake objects into pulumi resources and have all the python code for those resources. Recently I ran pulumi refresh to make sure the resources matched the state in snowflake and it deleted about 100 resources even though those resources still exist in snowflake. I have retainOnDelete and protect flags set on all the resources and can't figure out why they were deleted from pulumi state. Can anyone help with this?

Maybe a stupid question but I’ve created a polumi project locally … and I now want to move it to pulumi cloud … how can I do this ?

Sorry if I missed something, but I just tried to upgrade the pulumi-eks library to version 1.0.0 (python code). And I get the following error :

Exception: Invoke: Default provider for 'aws' disabled. 'aws:index/getPartition:getPartition' must use an explicit provider.

If I downgrade the lib to my previous version, it works again

👋 Hi everyone! Does anyone have a good Pulumi example of deploying API Gateway + Lambda (similar to serverless.yml inputs)?

Hey all. Has anyone had experience using Pulumi with PlanetScale?

Hey guys. I'm unable to install Pulumi when building a Docker container for local dev. The problem is that in the official install script,

TARBALL_DEST=$(mktemp -t pulumi.tar.gz.XXXXXXXXXX)

works but

EXTRACT_DIR=$(mktemp -d pulumi.XXXXXXXXXX)

fails with permission denied. Does anyone know how to fix this?

👋 Hi everyone! Is it possible in Pulumi to create logins on the fly for your operations maybe through some API (I have not checked the automation API to see if it supports the same, sorry about that). The use case is to run an API server that exposes certain routes which can help in creating of infra for a few different accounts based on the credentials passed in the request body. Any help on the same would be appreciated

Hi, I have an issue with a team member. I tried inviting him and he did a

pulumi up

, however pulumi says it basically has to update everything when run from his computer. We share the same repo obviously, I’m on Mac, he is on Windows. What could it be? Thanks a lot for the help, I can’t figure this out!

Hi, I want to know if multiple projects can use the same backend and same stack?

if I use the self-managed backend, does It not support the organization?

➜  test2 pulumi stack init broomllc/staging
warning: A new version of Pulumi is available. To upgrade from version '3.44.3' to '3.49.0', run 
   $ brew upgrade pulumi
or visit <https://pulumi.com/docs/reference/install/> for manual instructions and release notes.
error: stack names may not contain slashes

Hi, just upgraded from 3.48 to 3.49 and I’m getting this error when deploying:

CommandError: code: -2\n' +
    ' stdout: \n' +
    ' stderr: Command failed with exit code 255: pulumi stack select --stack settlemint/staging-ethereum-goerli-ade2 --non-interactive\n' +
    'error: stack names may not contain slashes\n' +
    ' err?: Error: Command failed with exit code 255: pulumi stack select --stack settlemint/staging-ethereum-goerli-ade2 --non-interactive\n' +
    'error: stack names may not contain slashes\n' +
    '\n' +
    '    at Object.createCommandError (/Users/adrienblavier/Documents/settlemint/bpaas/node_modules/.pnpm/@pulumi+pulumi@3.49.0/node_modules/@pulumi/automation/errors.ts:75:27)\n' +
    '    at Object.<anonymous> (/Users/adrienblavier/Documents/settlemint/bpaas/node_modules/.pnpm/@pulumi+pulumi@3.49.0/node_modules/@pulumi/automation/cmd.ts:84:15)\n' +
    '    at Generator.throw (<anonymous>)\n' +
    '    at rejected (/Users/adrienblavier/Documents/settlemint/bpaas/node_modules/.pnpm/@pulumi+pulumi@3.49.0/node_modules/@pulumi/pulumi/automation/cmd.js:19:65)\n' +
    '    at processTicksAndRejections (node:internal/process/task_queues:96:5)'

Hi everyone, First time writing here, want to say that I’m very exciting about the project! I’m reading docs on Pulumi Packages and wondering if I got it right that native providers can only be implemented with Go? That’s the only example I see in docs It might be obvious by the fact that pulumi itself is written on Go and “native” refers to that 🙂 But then I Iook at the “write once, use in all languages” pic here and it gives me hope that it’s not the case Also, does it support Java generation or maybe that’s at least on the horizon?

When using the

import

for ResourceOptions, is there a quick way to see what the differences are when presented with this warning?

warning: inputs to import do not match the existing resource; importing this resource will fail

Does anyone know what Pulumi does to get the json schema for terraform providers (that it uses for code-gen purposes) ?

Is there a way to tell which version of

terraform-provider-aws

the

pulumi-aws

provider is based on?