Hi all. I have put together an initial version of a component resource for installing Twingate connectors into GCP. It seems to be working for basic usage. It is here: https://github.com/activatedio/pulumi-google-twingate What are some recommended practices for handling namespaces and project names? This is a component provided by my company, so the NPM organization is “activatedio”, as is the GitHub, Given it is a pulumi component for installing Twingate on GCP, the npm module can be “@activatedio/pulumi-gcp-twingate”. Go is straightforward with the git path. What are the recommendations for .Net and Python?

Hi, I have been looking into using pulumi for a serverless app using AppSync and DynamoDB. To get started, I have decided to use the following template to get started, so authentication etc is handled for me: https://github.com/SimonHoiberg/saas-template Going through the project, it looks like a lot of work to set up just a single table with CRUD operations for a given entity. It it possible for anyone to provide a simple CRUD example for a given test entity in the context of the github repo linked? I have a hard time finding examples online, which I can use to figure it out myself. E.g. for a table to store an entity with a create operation, to me it looks like the steps are: • Create model in back-end/src/types • Create file and export "create" function in back-end/src/dynamodb/ • Create type and mutation in back-end/resources/schema/schema.graphql • Add table, set dynamoDBTables and export table id in back-end/resources/pulumi/dynamodb.ts • Create folder for each CRUD operation containing source-file and callback-file in back-end/resources/pulumi/resolvers/ So for a single operation, a folder with these two files: (back-end/resources/pulumi/resolvers/create-test-entity/create-test-entity.ts) and (back-end/resources/pulumi/resolvers/create-test-entity/source.ts) • Call setup<entity>Source file in back-end/resources/pulumi/appSync.ts Creating just the CRUD operations for a single entity is a lot of folders, files and code, and I still haven't even figured out how to pass parameters from the source.ts file to its corresponding callback handler (E.g. the object to be put in the database). Can it be as complex as I make it out to be?

Hello, I remember at PulumiUP event, someone (I think it was @quiet-wolf-18467) shared with me a tool that convert CRD to pulumi class, but I cannot find it again (or there is no such thing and I have terrible memory)

Hello, How can i open an enterprise support ticket?

I am not sure if slack or github issues is better but I have been dealing with issue for several days now, trying everything I can find in github issues, stack overflow and my own debugging in an attempt to find a solution but I am stuck I have an issue with

pulumi up

not being able to find the AWS credentials

Error: invocation of awsec2/getVpcgetVpc returned an error: unable to validate AWS AccessKeyID and/or SecretAccessKey - see https://pulumi.io/install/aws.html for details on configuration

I have a profile setup in my aws credentials file and I can view the config when using the CLI but cannot get it to work with the pulumi. I had it working before but for some reason it has stopped working and I cannot find any changes that would have caused it, at least through git. FYI, I am using a monorepo for all my services and using symlinks to pull in the

package.json

and

node_modules

(though even removing that has not helped). My

Pulumi.stack.yaml

in each service directory has the

aws:profile

and

aws:region

set

Can I set a specific email address to use for an organization, like I can do on GitHub? I signed up for Pulumi using my GitHub account - but for the work org I created, I need it to use my work email. Can I do that, or do I need to create a separate pulumi account for my work email?

apologies if this has been asked before but - does pulumi support a concept of a “base” stack configuration file, scoped in a particular project? eg: •

Pulumi.<base>.yaml

- has the defaults •

Pulumi.<a>.yaml

- has the

a

stack’s configs, as overrides from what is specified in

base

•

Pulumi.<b>.yaml

- has the

b

stack’s configs … etc.

I am not sure if this is an reopened bug related to https://github.com/pulumi/pulumi-eks/issues/571

+  pulumi:pulumi:Stack Galaxy-AWS_ECS-96471806 **creating failed** 1 error
 
Diagnostics:
  aws:iam:RolePolicyAttachment (task-definition-1142-execution-9a42f520):
    error: 1 error occurred:
    	* creating urn:pulumi:AWS_ECS-96471806::Galaxy::awsx:ecs:FargateTaskDefinition$aws:iam/rolePolicyAttachment:RolePolicyAttachment::task-definition-1142-execution-9a42f520: 1 error occurred:
    	* error reading IAM Role Managed Policy Attachment (task-definition-1142-execution-189233a:arn:aws:iam::aws:policy/service-role/AmazonECSTaskExecutionRolePolicy): couldn't find resource
 
  pulumi:pulumi:Stack (Galaxy-AWS_ECS-96471806):
    error: update failed

Even though I provide the ResouceOptions.transformations like lblackstone said:

{
          transformations: [
            // Update all RolePolicyAttachment resources to use aws-cn ARNs.
            args => {
              if (
                args.type ===
                'aws:iam/rolePolicyAttachment:RolePolicyAttachment'
              ) {
                const arn: string | undefined = args.props['policyArn'];
                if (arn && arn.startsWith('arn:aws:iam')) {
                  args.props['policyArn'] = arn.replace(
                    'arn:aws:iam',
                    'arn:aws-cn:iam'
                  );
                }
                return {
                  props: args.props,
                  opts: args.opts,
                };
              }
              return undefined;
            },
          ],
        }

Is there anyone encounter this issue during creating AWS ECS stack in cn-northwest-1 region? Thanks!

Is there a way to see the state backend that I’m logged in to?

pulumi whoami

just shows the username. But I don’t know if I’m logged into our custom GCP state, or pulumi service. (I can

pulumi logout && pulumi login

to be safe, but I want to programmatically determine backend for scripting)

I've been trying to find a decent description of this but couldn't find it anywhere. What is the difference between the "classic" and "native" version of plugins?

Im trying to reuse the github workflow to use pulumi preview . However im getting this error :GitHub Actions / .github/workflows/pull_request.yml Invalid workflow file

error parsing called workflow "peopleticker/ccc/.github/workflows/pull_request.yml@master": workflow was not found.

here is the code that I am using:

name: Call a reusable workflow

permissions:
  id-token: write
  contents: read

on:
  pull_request:

jobs:
  call-workflow-passing-data:
    uses: peopleticker/ccc/.github/workflows/pull_request.yml@master

Hi all, I have an issue with the AutoScalingGroup AWS. I need to specify my own userData in the launch configuration. Yet I am unable to remove the suffix from and therefore predict the stack name. As a result I can do whatever i want in my user data but can never send the signal to cloudformation and my stack creation always fail Any pointer on how to get out of this?

has anyone experienced an issue with a fully manually created ECS Cluster where the instance during it's creation does not have network access, but does later on ? I went through every bit of my config: • Security Group allow eggress anywhere • the instance is in the private subnet, which routing table for outbound traffic points to the NAT • The NAT Gateway is in public subnet • the pub subnet does have an IG Additionally I created a jumbox and while the stack fails to create (no network so no cfn-signal installed by cloud-init and sent to Cloud formation for the autoscaling group). Once the instance is up, and without changing anything I log in to that specific and can successfully reach internet... confirming that the setup is right. I am thinking that the instance comes up before the NAT is attached or a specific rule added to routing table or Security group. Any pointer would be welcomed

Hi, in the last couple of weeks I've noticed that sometimes, when using

--target

, both

pulumi pre

and

pulumi up

will show only the resources that I want to update (good), but after confirming that I want to perform the update, Pulumi will try to update a resource that I haven't explicitly requested, causing failures. Has anyone seen this behaviour before?

I have not been able to find anything that will let me bootstrap Flux with Pulumi (like this for terraform). If anyone know of something I have missed here, I would love to see it before I invest more time on this on my own.

Hey all, I need to run an inline program inside a docker container image. Since I can’t directly install Pulumi, I’m using precompiled binaries and would like to add them to the Pulumi PATH env var. Inside my program, I can get the absolute path to be binary file, and if I run it programmatically, it works OK. but if I add this location to the PATH and pass that auto.LocalWorkspaceOptions inside envvars, the Pulumi SDK can’t find pulumi executable. Any ideas? Using Golang.

Is it possible to conditionally create resources?

if <condition>: 
    my_lambda = aws.lambda_.Function(...)

When I tried this, the if statements seem to be ignored. I'm trying to create or ignore resources based on the current pulumi stack

Pulumi is complaining: error deleting Target Group: ResourceInUse: Target group ‘arnawselasticloadbalancing:XXX’ is currently in use by a listener or a rule I think I understand the reason but how could I make a stack update then? Should I update it in two pass? (one removing the Listener first?)

Hey folks. I've been having an issue with the

atlastCidrBlock

in a managed

mongodbatlas.NetworkPeering

resource using the Node version of pulumi. The option seems to have no effect and the created resource seems to always have the default value of

192.168.248.0/21

.

export const atlasPeer = new mongodbatlas.NetworkPeering('atlas-peer', {
  providerName: "AWS",
  awsAccountId: AWS_ACCOUNT_ID,
  vpcId: VPC_ID,
  projectId: ATLAS_PROJECT_ID,
  containerId: mongoCluster.containerId,
  accepterRegionName: AWS_REGION,
  routeTableCidrBlock: '10.11.0.0/16',
  atlasCidrBlock: '192.168.232.0/21',
});

This snippet creates a stack output of

{
  "accepterRegionName": "us-west-2",
  "atlasCidrBlock": "192.168.232.0/21",
  "atlasGcpProjectId": "",
  "atlasId": "XXXXXXXXXX",
  "atlasVpcName": "",
  "awsAccountId": "999999999",
  "azureDirectoryId": "",
  "azureSubscriptionId": "",
  "connectionId": "pcx-XXXXXXXX",
  "containerId": "XXXXXXXXXX",
  "errorMessage": "",
  "errorState": "",
  "errorStateName": "",
  "gcpProjectId": "",
  "id": "XXXXXXXXX",
  "networkName": "",
  "peerId": "XXXXXXXXX",
  "projectId": "XXXXXXXX",
  "providerName": "AWS",
  "resourceGroupName": "",
  "routeTableCidrBlock": "10.11.0.0/16",
  "status": "",
  "statusName": "PENDING_ACCEPTANCE",
  "urn": "urn:pulumi:staging::journey::mongodbatlas:index/networkPeering:NetworkPeering::atlas-peer",
  "vnetName": "",
  "vpcId": "vpc-00000000"
}

...with an

atlasCidrBlock

of

192.168.232.0/21

, though the created peering connection instead has the default Atlas CIDR of

192.168.248.0/21

, as does its corresponding route table entry on my aws side. Interestingly, the stack output's value for atlasCidrBlock doesn't even change across

pulumi refresh

operations. Is it possible I'm doing something wrong? If not, is this most likely a bug with pulumi or with atlas? Thanks!

Hi, awesome people 👋 Having a weird issue with deploying Lambda@Edge functions using

aws.lambda.CallbackFunction

. For some reason, Pulumi started deploying these functions included a big portion of

node_modules

in the package, which deploys a package size of +15.5 MB (which is too big to use as a Lambda Edge. I have tried stripping everything in the function and making sure to prevent any open closures, basically reducing it to

callback: () => {}

. No matter what I do, it keeps including

node_modules

in the lambda package itself. It used to worked perfectly, now I have zero idea what I suddenly did wrong to trigger this. Any ideas how I can debug this, or how I can force-exclude

node_modules

from the package?

Hey All! I wanted to know am I capable of using Pulumi in order to modify a specific lambda I have already deployed> I want to add subscription filters to a few lambdas that I already have. Thanks in advance to anyone who is willing to help! 😄

Pulumi does a nice job of generating code for resources I

pulumi import

. Is there any way to get pulumi to generate this code without actually importing the infra into my stack? I’d prefer to use the “`import` resource” option to manage my stack state, but I still find the code generation very helpful.

Hi All,

Been checking out Pulumi, and I'm having a hard time understanding what Pulumi can offer outside of what is already available in AWS cdk. I've looked at some tutorials and such, but I still haven't seen what I think is a big difference. Could someone enlighten me?

Is there a Pulumi provider for Google Cloud Looker ?

Hi, i am pretty new to pulumi. And I want to popluate a pretty big stack, based on some information that i can retrieve from an webservice. Why should it be a bad idea to dynamically determine the resources to create while the host-language runs. The only thing i can think of is possible differences between pulumi preview and pulumi up. Thanks in advance to show my, why this is could be a bad idea.

Hi guys, I'm implementing some pulumi policy pack, but it seems on a policy pack project is not possible using the pulumi functions like (aws.ec2.get_vpc) or similar like that. When I trying to use one of this I get the following error. Do you guys know if is there a proper way to use this functions on a policy pack? btw if I use this on a pulumi project there is no errors

Hi guys! How can I install kubeflow on GKE using pulumi. I don't see in the documentation. Any Help will be appreciated.

Thanks in advance