I figure I can include it in one stack, export it as an output and then use a stack reference in the 2nd project... but idk, feels like there might be a better option

Hey guys! I’m having an issue where running

pulumi up

will protect everything without me asking it to protect them. Any ideas at steps I can take to fix this?

crossposting for vis

Hello everyone, i have been integrating pulumi for integrating with api gateway but I ran into some issue.

ids:list[pulumi.output.Output] =[] #contains ids of the resources to be deployed
deployment = apigateway.Deployment("test_deployment",
        rest_api=restapi.id,
        triggers={
            "redeployment":pulumi.Output.all(ids)
            .apply(lambda exampleResourceId: json.dumps([exampleResourceId]))
            .apply(lambda to_json: hashlib.sha1(to_json.encode()).hexdigest()),      
        }
    )

as pulumi.Output.all function accepts the pulumi.output.Output not list[pulumi.output.Output], I am getting error. How should I pass the above ids into pulumi.Output.all function so that all the ids in the list can passed? (a list can contain any number of elements)

Cleanup: Is there any helpers for cleaning up dev/test-ish stacks? I see I can use tags on stacks, but no way of using a filter on

destroy

or

rm

. I could ofc do it myself using

pulumi stack ls --tag isDevTempEnv true

and then destroy them one by one in a loop.

hi... I would like to create an IAM role that a) Allows AssumeRole, b) Has several Customer managed policies attached, c) Has several AWS managed policies attached. What would the python pulumi format of such a role be?

Hi, I published SDK npm into private GitHub packages. when I am using it in dependencies pulumi is not able to perform IaC operations. may be the binaries not coming into the SDK folder.

Updating (dev)

View Live: <https://app.pulumi.com/Atmakur/s3-service/dev/updates/2>

Type                 Name            Status

pulumi:pulumi:Stack  s3-service-dev

Resources:

1 unchanged

Duration: 1s

Hi guys, does somebody know how to skip a pulumi policy when the resources are destroyed using, currently, we have some issues with some resources that we will destroy in the stack, the policies still validating those resources

Hi All, Please help. When upgrading pulumi/azure from 4 to 5 I got below error. Please share if any solution for this?

panic: interface conversion: interface {} is nil, not []interface {}
    goroutine 242 [running]:
    <http://github.com/hashicorp/terraform-provider-azurerm/internal/services/containers/migration.KubernetesClusterV1ToV2.UpgradeFunc.func1({0x6eee980|github.com/hashicorp/terraform-provider-azurerm/internal/services/containers/migration.KubernetesClusterV1ToV2.UpgradeFunc.func1({0x6eee980>?, 0xc0028888c8?}, 0x5c70b80?, {0xc0029ccfc0?, 0x6eee980?})
        /home/runner/go/pkg/mod/github.com/pulumi/terraform-provider-azurerm@v1.41.1-0.20220923214953-9abea3c6f19c/internal/services/containers/migration/kubernetes_cluster.go:1231 +0x2fe
    <http://github.com/hashicorp/terraform-provider-azurerm/internal/tf/pluginsdk.StateUpgrades.func1({0x6eeb650|github.com/hashicorp/terraform-provider-azurerm/internal/tf/pluginsdk.StateUpgrades.func1({0x6eeb650>, 0xc000138028}, 0x2?, {0x5c19d60, 0xc000e4ae00})

Hi! I have a plan deploy many service on on-premise kubernetes. So, maybe need many stacks. Most are in-house services. Not public. I read team plan has unlimited stacks. How many can create stacks in Individual plan?

I’m trying to find out where plugins are downloaded from, but I haven’t had any luck yet. How can I construct the URL for a plugin, so that I can download it without using the CLI?

goooood afternoon! We are recently experiencing a bunch of errors that look like the following - and we're all a wee bit stumped; anyone had experience with these and knows what is going on? Diagnostics: kubernetes:helm.sh/v3:Release (credtest-cert-manager): error: rendered manifests contain a resource that already exists. Unable to continue with install: could not get information about the resource ClusterRole "credtest-cert-manager-c155c92a-controller-cer tificates" in namespace "": Get "https://azurenp-4ed01735.hcp.switzerlandnorth.azmk8s.io:443/apis/rbac.authorization.k8s.io/v1/clusterroles/credtest-cert-manager-c155c92a-controller-certificates ": remote error: tls: bad record MAC

Hi, is there a way to do a

pulumi state delete <urn>

programmatically in Python or via REST API?

When building a dynamic provider, is there a way to ignore updates to the provider?

[diff: ~__provider]

it seems to try to update the resource even though the its only the provider version that has changed. I notice on the official providers, these type of diffs get ignored.

I'm trying to replace a reference with a stub: essentially an aws VPC object with a mostly empty ComponentResource. https://gist.github.com/sheenobu/a58297508055a3e4c83aee1b5f38432e I'm getting

... (...-vpc):
    error: expected '::' in provider reference ''

Maybe you can't replace a resource from the AWS provider for one from a different provider? or is my aliases: wrong?

Hi guys, I am new to pulumi, is there any starter to start a infra with s3, cloudfront, eks, loadBalancer?

Hi guys, I am trying to import a GCP budget alert in pulumi, and I notice the doc mentions setting

user_project_override

to true in the provider config. Does anyone have an example? Link to doc: https://www.pulumi.com/registry/packages/gcp/api-docs/billing/budget/

Good afternoon. We are new to Pulumi and on a teams account. We need to generate an access token for the organization and the admin is on vacation, how can we get another user granted that access?

Hi all, I'm looking for some advice on Pulumi project/stack design from those more experienced with it than I. I'm trying to figure out how tightly-coupled different stacks that reference each other via outputs and stack references are. As far as I understand, such references would create a tight dependency between the stack that produces a value and the stack that consumes the value. If the output value changed on the producing side (perhaps it was a computed value or something), then that would immediately invalidate the consuming side's value such that the next time that consuming stack is deployed (

pulumi up

) it will use the new value, correct? If that's true, then is there some way to take advantage of outputs and stack references that still allows for a looser coupling? My goal is to strongly limit the blast radius of stack changes. I'd like to be that if we change one stack, that those changes don't automatically ripple to many others. What's the best practice here?

Is there a specific channel for reporting broken APIs?

Is there any way to interpolate pulumi Outputs into a JSON stringified IAM policy w/o wrapping the entire resource creation in an

apply

? Example:

const scsExecPolicy = pulumi
  .all([commonClusterExecKey.arn, commonClusterEcsExecLogGroup.arn])
  .apply(([commonClusterExecKeyARN, commonClusterEcsExecLogGroupArn]) => {
    return new aws.iam.Policy("scs-exec-policy", {
      name: "cfx-policy-scs-exec",
      policy: JSON.stringify({
        Version: "2012-10-17",
        Statement: [
          {
            Action: [
              "ssmmessages:CreateControlChannel",
              "ssmmessages:CreateDataChannel",
              "ssmmessages:OpenControlChannel",
              "ssmmessages:OpenDataChannel",
            ],
            Effect: "Allow",
            Resource: "*",
          },
          {
            Action: ["logs:DescribeLogGroups"],
            Effect: "Allow",
            Resource: "*",
          },
          {
            Action: [
              "logs:CreateLogStream",
              "logs:DescribeLogStreams",
              "logs:PutLogEvents",
            ],
            Effect: "Allow",
            Resource: `${commonClusterEcsExecLogGroupArn}:*`,
          },
          {
            Effect: "Allow",
            Action: ["kms:Decrypt"],
            Resource: commonClusterExecKeyARN,
          },
        ],
      }),
    });
  });

Is there any way to Enable enhanced networking with the Elastic Network Adapter (ENA) on Linux instances by pulumi. I searched for the resources but no luck

Mono-stack vs multi-stack question: I'm thinking of generating all of my company's GitHub repos using Pulumi. Permissions, Organizations, build variables, branch settings, PR templates, etc. would all be managed with Pulumi. Would it make the most sense to have all repos in a single Pulumi stack? Or to have each repo in its own stack? It'll be about 70 repos in the next few months and +3/week from then on.

Hello all, looked at Pulumi for some time now. Looking at it from remote runner perspective and new language adoption. Did you ever consider leveraging WebAssembly (WASM) with or without System interface (WASI)? For example to sandbox an executed code and to expand quickly to all languages that compile to WASM. Got an inspiration from Kubewarden (policy as code) and Envoy proxy (wasm filters)

Is there a way to move existing infrastructure into component resources without deleting/recreating anything?

Hey all, I am having issues creating a namespace and referencing that namespace name while using the kubernetes.core.v1.Namespace (kubernetes provider). The namespace name I want is

istio-system

, but a randomly generated string gets appended to the name. Is there a way to specify a specific name for a namespace when using

new kubernetes.core.v1.Namespace

?

const istioNamespaceName = "istio-system"

const istioNamespace = new k8s.core.v1.Namespace(istioNamespaceName);

const istioVersion = "1.15.0";

const istioBase = new k8s.helm.v3.Chart("istio-base", {
    chart: "base",
    version: istioVersion,
    namespace: istioNamespaceName,
    fetchOpts: {
        repo: "<https://istio-release.storage.googleapis.com/charts>",
    },
}, {
    dependsOn: istioNamespace
});

👋 I’m trying to deploy an update to a Slack App I made. If I run

pulumi up

I get:

error modifying Lambda Function (lambda-name) Code: RequestEntityTooLargeException: status code: 413

If I run

pulumi up

again, it looks like the changes go through:

Type                    Name                                      Status      Info
     pulumi:pulumi:Stack     lambda-name                                
 ~   ├─ aws:lambda:Function  lambda-slash-commands  updated     [diff: ~code]
 ~   └─ aws:lambda:Function  lambda-cron            updated     [diff: ~code]

Resources:
    ~ 2 updated
    17 unchanged

If I then go and look for the changes in the Slack App, they’re not there. Side Note - I know I need to address the

RequestEntityTooLargeException

. I tried adding webpack to reduce the build size but that resulted in an error where Webpack doesn’t know what to do with

@pulumi/aws

and that dead-ended me there. Any thoughts on why the updates appear to successfully go through but don’t?

Hey everyone, I've been running into an issue when deploying my stacks recently. I have several projects that use Azure-Native, and recently if I run a

pulumi refresh

and then try to run

pulumi up

I have been getting this error. Running

pulumi destroy

first allows me to successfully use

pulumi up

but it is annoying to have to do this, especially with certain resources that take a long time to remove and deploy. This also doesn't seem to happen if I don't run the

refresh

before running the up command. Can anyone provide insight into what this error is and/or what might be causing it? I am using Pulumi 3.40.1. We are deploying resources to azure using the Azure-Native and pulumi standard packages. Let me know what other information I can provide in order to diagnose this issue. Thanks in advance.

Hello Pulumi masters, I am wondering if anyone of you have a recommendation on how to use a single API Gateway across multiple repos so I can keep the same base domain. I want to be able to add routes to an existing Gateway vs recreate the gateway.