Hello! I have a problem where i have a parent/child resource pair where the child depends on the parent existing. In a case where the parent has to be replaced, pulumi is trying to delete the parent before creating a new one (delete before replace is not set), but the api call fails because the child is referencing the paret. Is there a way to get around it? In this case it is

awsnative.wafv2.WebAcl

/

awsnative.wafv2.WebAclAssociation

, but i have had similar problems in the past with certificates.

👋 hi is there a way to restore my state to a previous state? I’m using Pulumi as the backend

Hello

Is there a way to use the cross guard in automation API?...Am able to use it via CLI..

👋 hi again. I have a GKE cluster with 1 nodepool. I want to either (1) add another nodepool, or (2) change the node type of the existing nodepool. But pulumi wants to recreate the entire cluster, and delete everything that depends on the cluster before doing so. Is there a way to add/update a nodepool without recreating the entire cluster??

Has anyone else experienced issues with pulumi.Command running within github actions?

+  command:local:Command pro-sto-site-sync creating error: transport is closing
 +  command:local:Command pro-sto-site-sync **creating failed** error: transport is closing
    pulumi:pulumi:Stack platform-production running panic: runtime error: invalid memory address or nil pointer dereference
    pulumi:pulumi:Stack platform-production running [signal SIGSEGV: segmentation violation code=0x1 addr=0x0 pc=0xc07034]
    pulumi:pulumi:Stack platform-production running goroutine 9 [running]:
    pulumi:pulumi:Stack platform-production running <http://github.com/pulumi/pulumi-command/provider/pkg/provider.(*command).run(0xc00007aae0|github.com/pulumi/pulumi-command/provider/pkg/provider.(*command).run(0xc00007aae0>, 0xf219e0, 0xc000382e40, 0xc000038600, 0x57, 0xc0000ad3b0, 0xc00003c2a0, 0x6a, 0x0, 0x0, ...)
    pulumi:pulumi:Stack platform-production running 	/home/runner/work/pulumi-command/pulumi-command/provider/pkg/provider/command.go:115 +0x794
    pulumi:pulumi:Stack platform-production running <http://github.com/pulumi/pulumi-command/provider/pkg/provider.(*command).RunCreate(0xc00007aae0|github.com/pulumi/pulumi-command/provider/pkg/provider.(*command).RunCreate(0xc00007aae0>, 0xf219e0, 0xc000382e40, 0xc0000ad3b0, 0xc00003c2a0, 0x6a, 0x0, 0x0, 0x0, 0x0)
    pulumi:pulumi:Stack platform-production running 	/home/runner/work/pulumi-command/pulumi-command/provider/pkg/provider/command.go:50 +0x93
    pulumi:pulumi:Stack platform-production running <http://github.com/pulumi/pulumi-command/provider/pkg/provider.(*commandProvider).Create(0xc000109b00|github.com/pulumi/pulumi-command/provider/pkg/provider.(*commandProvider).Create(0xc000109b00>, 0xf21a88, 0xc00007f560, 0xc00007cb90, 0x0, 0x0, 0x0)
    pulumi:pulumi:Stack platform-production running 	/home/runner/work/pulumi-command/pulumi-command/provider/pkg/provider/provider.go:197 +0xe85
    pulumi:pulumi:Stack platform-production running <http://github.com/pulumi/pulumi/sdk/v3/proto/go._ResourceProvider_Create_Handler.func1(0xf21a88|github.com/pulumi/pulumi/sdk/v3/proto/go._ResourceProvider_Create_Handler.func1(0xf21a88>, 0xc00007f560, 0xdad2e0, 0xc00007cb90, 0xdbbac0, 0x1471400, 0xf21a88, 0xc00007f560)
    pulumi:pulumi:Stack platform-production running 	/home/runner/go/pkg/mod/github.com/pulumi/pulumi/sdk/v3@v3.19.0/proto/go/provider.pb.go:2602 +0x89
    pulumi:pulumi:Stack platform-production running <http://github.com/grpc-ecosystem/grpc-opentracing/go/otgrpc.OpenTracingServerInterceptor.func1(0xf21a88|github.com/grpc-ecosystem/grpc-opentracing/go/otgrpc.OpenTracingServerInterceptor.func1(0xf21a88>, 0xc00007f230, 0xdad2e0, 0xc00007cb90, 0xc0000305a0, 0xc00000c8d0, 0x0, 0x0, 0xf0f3a0, 0xc00009d6e0)
    pulumi:pulumi:Stack platform-production running 	/home/runner/go/pkg/mod/github.com/grpc-ecosystem/grpc-opentracing@v0.0.0-20180507213350-8e809c8a8645/go/otgrpc/server.go:57 +0x30a
    pulumi:pulumi:Stack platform-production running <http://github.com/pulumi/pulumi/sdk/v3/proto/go._ResourceProvider_Create_Handler(0xdce940|github.com/pulumi/pulumi/sdk/v3/proto/go._ResourceProvider_Create_Handler(0xdce940>, 0xc000109b00, 0xf21a88, 0xc00007f230, 0xc00007aa80, 0xc0000c38c0, 0xf21a88, 0xc00007f230, 0xc0003aca80, 0x34a)
    pulumi:pulumi:Stack platform-production running 	/home/runner/go/pkg/mod/github.com/pulumi/pulumi/sdk/v3@v3.19.0/proto/go/provider.pb.go:2604 +0x150
    pulumi:pulumi:Stack platform-production running <http://google.golang.org/grpc.(*Server).processUnaryRPC(0xc000249880|google.golang.org/grpc.(*Server).processUnaryRPC(0xc000249880>, 0xf29e38, 0xc0000bf500, 0xc0003965a0, 0xc000109b90, 0x14344a0, 0x0, 0x0, 0x0)
    pulumi:pulumi:Stack platform-production running 	/home/runner/go/pkg/mod/google.golang.org/grpc@v1.37.0/server.go:1217 +0x52b
    pulumi:pulumi:Stack platform-production running <http://google.golang.org/grpc.(*Server).handleStream(0xc000249880|google.golang.org/grpc.(*Server).handleStream(0xc000249880>, 0xf29e38, 0xc0000bf500, 0xc0003965a0, 0x0)
    pulumi:pulumi:Stack platform-production running 	/home/runner/go/pkg/mod/google.golang.org/grpc@v1.37.0/server.go:1540 +0xd0c
    pulumi:pulumi:Stack platform-production running <http://google.golang.org/grpc.(*Server).serveStreams.func1.2(0xc0002fc260|google.golang.org/grpc.(*Server).serveStreams.func1.2(0xc0002fc260>, 0xc000249880, 0xf29e38, 0xc0000bf500, 0xc0003965a0)
    pulumi:pulumi:Stack platform-production running 	/home/runner/go/pkg/mod/google.golang.org/grpc@v1.37.0/server.go:878 +0xab
    pulumi:pulumi:Stack platform-production running created by <http://google.golang.org/grpc.(*Server).serveStreams.func1|google.golang.org/grpc.(*Server).serveStreams.func1>
    pulumi:pulumi:Stack platform-production running 	/home/runner/go/pkg/mod/google.golang.org/grpc@v1.37.0/server.go:876 +0x1fd
 +  command:local:Command pro-dev-docs-sync creating error: connection error: desc = "transport: Error while dialing dial tcp 127.0.0.1:38829: connect: connection refused"
 +  command:local:Command pro-dev-docs-sync **creating failed** error: connection error: desc = "transport: Error while dialing dial tcp 127.0.0.1:38829: connect: connection refused"

Hi, is it possible to have

pulumi stack graph

take into account implicit dependencies, not just explicit?

Anyone have any prior art anywhere using pulumi as a library? I want to wrap it in a cli with additional functionality.

Our team is unable to delete stacks using

pulumi stack rm

. When they attempt to do so, they get this error:

error: [403] You do not have permission to perform this operation.

Increasing the verbosity hasn’t provided any more information. I am able to delete them with no issue (note I am an admin for our team). Thank you!

Hi, I'm sure this question gets asked all the time. Any news on when

awsx

for Python will be available? Our team feels stuck with AWS CDK until it is.

Hello, having a little trouble with a private AKS cluster (https://www.pulumi.com/registry/packages/azure-native/api-docs/containerservice/managedcluster/#userassignedidentities_csharp) and user assigned identities

Hi, I have defined the

kubernetes.Provider

to use the default path

~/.kube/config

:

k8s_provider = kubernetes.Provider("k8s")

But if I try to access the

k8s_provider.kubeconfig

argument it is empty. For example if I try to reference it in a secret:

secrets = kubernetes.core.v1.Secret(
    "secrets",
    metadata={
        "name": "secrets",
    },
    string_data={
        "key": "value",
        "KUBECONFIG": k8s_provider.kubeconfig,
    },
    opts=ResourceOptions(provider=k8s_provider),
)

Hi, I want to invoke below API:

pulumi_gcp.appengine.Application.get(resource_name, unique_provider_id)

Anyone knows where I can get the value for second parameter?

Hi Question around best practices. We are currently upscaling to multi region deployments and creating our stack from scratch. We created an AWS organisation and we will be creating different accounts here for different prod accounts. We have existing iam admin users in our management AWS account and they will be used for assuming a role for different test/prod accounts to interact with those accounts I am wondering what is the best practice with pulumi. How we are visualising our suite at present is to have projects with multiple stacks where each stack is pointing to an environment. However regarding the creds for the AWS account we are under a slight dilemma. We have considered two options, both we like and dislike at the same time. 1. Create iam users in the child AWS accounts aswell and use those credentials for pulumi. However with a growing number of regions this means a fair amount of creds to store and switch between each stack deployment. 2. Use the iam user in the management account, use the single set of credentials of the user for all resources and stacks by creating a provider which assumes the role and making the account id configurable, however this means we will need to pass in the provider across every resources we create and if someone misses using the provider it ll be devastating. I am wondering if there is any best practices that pulumi suggests in this scenario.

How does Pulumi's secrets encryption work? Which protocols, hashing algos, key sizes, etc are used

I am running into a curses problem with pulumi-kubernetes + pulumi-kubernetes-ingress-nginx. I have pip installed

windows-curses

, and re-installed both pip packages. I get the following error:

Diagnostics:
  pulumi:pulumi:Stack (pulumi-kubecost-dev):
    error: Program failed with an unhandled exception:
    error: Traceback (most recent call last):
      File "C:\ProgramData\chocolatey\lib\pulumi\tools\Pulumi\bin\pulumi-language-python-exec", line 107, in <module>
        loop.run_until_complete(coro)
      File "C:\Python39\lib\asyncio\base_events.py", line 642, in run_until_complete
        return future.result()
      File "C:\GitHub\pulumi-kubecost\venv\lib\site-packages\pulumi\runtime\stack.py", line 126, in run_in_stack
        await run_pulumi_func(lambda: Stack(func))
      File "C:\GitHub\pulumi-kubecost\venv\lib\site-packages\pulumi\runtime\stack.py", line 49, in run_pulumi_func
        func()
      File "C:\GitHub\pulumi-kubecost\venv\lib\site-packages\pulumi\runtime\stack.py", line 126, in <lambda>
        await run_pulumi_func(lambda: Stack(func))
      File "C:\GitHub\pulumi-kubecost\venv\lib\site-packages\pulumi\runtime\stack.py", line 149, in __init__
        func()
      File "C:\ProgramData\chocolatey\lib\pulumi\tools\Pulumi\bin\pulumi-language-python-exec", line 106, in <lambda>
        coro = pulumi.runtime.run_in_stack(lambda: runpy.run_path(args.PROGRAM, run_name='__main__'))
      File "C:\Python39\lib\runpy.py", line 285, in run_path
        return _run_code(code, mod_globals, init_globals,
      File "C:\Python39\lib\runpy.py", line 87, in _run_code
        exec(code, run_globals)
      File ".\__main__.py", line 3, in <module>
        from curses import meta
      File "C:\Python39\lib\curses\__init__.py", line 13, in <module>
        from _curses import *
    ModuleNotFoundError: No module named '_curses'
    error: an unhandled error occurred: Program exited with non-zero exit code: 1

Does anyone know if there are plans to support a slimmed down version of the official pulumi docker image (like say with Alpine Linux)? The official image is pushing 4GB uncompressed, not ideal for some CI systems.

I'm deleting a stack (due to getting things in a tangle and needing to REDO FROM START) and it seems that the stack has resources which depend on other resources and get deleted when the parent resource is deleted, and then pulumi tries to delete them, as they were created after the parents. This of course fails, and then I need to edit the state to match reality and then I can proceed with deleting the rest of the stack. e.g. I created a ClusterRoleBinding after the EKS cluster it was in and now pulumi is trying to delete it after deleting the cluster. This is fine, and I can fix it. But could I have declared the RoleBinding in a way that pulumi knew that deleting the cluster would delete it or that it depends on the cluster and thus should be deleted first?

Hi, has anyone used

aws.dlm.LifecyclePolicy

? (im trying to create ebs snapshots on a cron) I tried to run the one in the docs but am running into this error

raise AssertionError(f"Unexpected type. Expected 'list' got '{typ}'")
    AssertionError: Unexpected type. Expected 'list' got '<class 'str'>'

and am not sure what’s causing this

Question on Helm Release: How do I enable additional tracing output when running pulumi helm. I am trying to deploy a release via pulumi that times out saying some resources are not yet ready. However, helm install of the same chart from command line helm goes through. I am trying to see how pulumi can give me more debug context - and if this is something i can control via any knobs. [I am deploying via pulumi automation api + python]

Hi guys, Let me ask a question about Pulumi pricing model. Recently I knew this posted blog (https://www.pulumi.com/blog/announcing-new-usage-based-pricing-for-your-whole-team/) about new pricing model of Pulumi (I didn't realize it until now...). According to the blog post, the new pricing model, Team edition, has a pricing structure that consumes credit according to each resource. However, our Pulumi account has an old pricing model, and the Team Starter plan is a model that pays by the number of team members like the attached image. Can we continue to use Pulumi with the old pricing model? Or will it be forced to move to a new pricing model? We have a lot of resources managed on Pulumi, and we are worried that one day we may suddenly get a high bill....

I'm trying to use pulumi helm release (python based). The chart's deployment fails with a timeout. Below is the error:

Diagnostics:
  pulumi:pulumi:Stack (test-trial2):
    Python 3.6 is approaching EOL and will not be supported in Pulumi soon. Check <https://github.com/pulumi/pulumi/issues/8131> for more details

    debug: registering resource: ty=pulumi:pulumi:Stack, name=test-trial2, custom=False, remote=False
    debug: registering resource: ty=pulumi:providers:kubernetes, name=my-k8s, custom=True, remote=False
    debug: registering resource: ty=kubernetes:<http://helm.sh/v3:Release|helm.sh/v3:Release>, name=trial-edge, custom=True, remote=False
    debug: Waiting for outstanding RPCs to complete
    debug: RPCs successfully completed
    debug: Waiting for 55 outstanding tasks to complete
    debug: beginning rpc register resource
    debug: beginning rpc register resource
    debug: beginning rpc register resource
    debug: beginning rpc register resource outputs
    debug: resource registration prepared: ty=pulumi:pulumi:Stack, name=test-trial2
    debug: resource registration successful: ty=pulumi:pulumi:Stack, urn=urn:pulumi:trial2::test::pulumi:pulumi:Stack::test-trial2
    debug: resource registration prepared: ty=pulumi:providers:kubernetes, name=my-k8s
    debug: register resource outputs prepared: urn=urn:pulumi:raji-trial2::test::pulumi:pulumi:Stack::test-trial2, props=
    debug: resource registration successful: urn=urn:pulumi:raji-trial2::test::pulumi:pulumi:Stack::test-trial2, props=
    debug: resource registration successful: ty=pulumi:providers:kubernetes, urn=urn:pulumi:trial2::test::pulumi:providers:kubernetes::my-k8s
    debug: resource registration prepared: ty=kubernetes:<http://helm.sh/v3:Release|helm.sh/v3:Release>, name=trial-edge
    error: update failed
    debug: resource registration successful: ty=kubernetes:<http://helm.sh/v3:Release|helm.sh/v3:Release>, urn=urn:pulumi:trial2::test::kubernetes:<http://helm.sh/v3:Release::trial-edge|helm.sh/v3:Release::trial-edge>

  kubernetes:<http://helm.sh/v3:Release|helm.sh/v3:Release> (trial-edge):
    warning: Helm release "trial-edge-8kchrd9c" was created but has a failed status. Use the `helm` command to investigate the error, correct it, then retry. Reason: timed out waiting for the condition
    error: 1 error occurred:
        * Helm release "trial-edge/trial-edge-8kchrd9c" was created, but failed to initialize completely. Use Helm CLI to investigate.: failed to become available within allocated timeout. Error: Helm Release trial-edge/trial-edge-8kchrd9c: timed out waiting for the condition

The same chart goes through fine when deploying manually (helm status shows deployed as well). All k8s objects are created properly in both the cases. How do I need to debug this further?

Hi, are there best practices/example repositories on how to split the infrastructure (AWS EKS, GCP GKE, ...) and the applications (helm charts)? Thanks

Hi I am trying to export outputs from resources created inside a loop using typescript. However the accountOutput is always empty. I am wondering whats the right approach to do this.

let accountDetails = [
    {name: 'test', email: '<mailto:testt@example.io|testt@example.io>', environment: 'test', billingInfoAccess: 'ALLOW'}
];

var accountOutput: { accountName: string, accountId: string }[] = [];

for (const accountDetail of accountDetails) {
    const account = new aws.organizations.Account(accountDetail.name, {
        email: accountDetail.email,
        iamUserAccessToBilling: accountDetail.billingInfoAccess,
        name: accountDetail.name,
        tags: {
            Environment: accountDetail.environment
        },
    });

    account.arn.apply(arn => {
        console.log(arn);
        accountOutput.push({accountName: accountDetail.name, accountId: arn})
    })
};


export const outputs = {
    accountInfo: accountOutput,
}

Hi, I'm new to plumi and trying to run the cli inside AWS code build. I'm using an

S3

bucket as the backend. I believe the

Pulumi.<stack>.yaml

should not be committed (pls correct me if I'm wrong). May I please know the recommended way of setting the configs? Should I set the each config from environment variable using

pulumi config set/set-all

command? If so How should I set the

secretsprovider

and the

encryptedkey

? Or can I retrieve those configs from backend?

Hi I created a project and it was created under my personal profile rather than my org account which I am linked to, how do I switch between both in cli, also can I transfer an existing project in my personal account to organisation?

👋 Hi everyone!

Hello everyone, is there a way to have multiple

__main__.py

files in Python? So I can be able to split users, databases, roles, etc.. Currently using Pulumi for the first time and I am trying to manage some Snowflake resources using pulumi_snowflake

👋 Hi all, I’m trying to create a simple

gcp.container.NodePool

, but

pulumi up

keeps failing with a 404:

gcp:container:NodePool (dev-gcp-us-east1-pool2):
    error: 1 error occurred:
    	* creating urn:pulumi:dev::infra::gcp:container/nodePool:NodePool::dev-gcp-us-east1-pool2: 1 error occurred:
    	* error creating NodePool: googleapi: got HTTP response code 404 with body: <!DOCTYPE html>
    <html lang=en>
      <meta charset=utf-8>
      <meta name=viewport content="initial-scale=1, minimum-scale=1, width=device-width">
      <title>Error 404 (Not Found)!!1</title>
      <style>
        *{margin:0;padding:0}html,code{font:15px/22px arial,sans-serif}html{background:#fff;color:#222;padding:15px}body{margin:7% auto 0;max-width:390px;min-height:180px;padding:30px 0 15px}* > body{background:url(//www.google.com/images/errors/robot.png) 100% 5px no-repeat;padding-right:205px}p{margin:11px 0 22px;overflow:hidden}ins{color:#777;text-decoration:none}a img{border:0}@media screen and (max-width:772px){body{background:none;margin-top:0;max-width:none;padding-right:0}}#logo{background:url(//www.google.com/images/branding/googlelogo/1x/googlelogo_color_150x54dp.png) no-repeat;margin-left:-5px}@media only screen and (min-resolution:192dpi){#logo{background:url(//www.google.com/images/branding/googlelogo/2x/googlelogo_color_150x54dp.png) no-repeat 0% 0%/100% 100%;-moz-border-image:url(//www.google.com/images/branding/googlelogo/2x/googlelogo_color_150x54dp.png) 0}}@media only screen and (-webkit-min-device-pixel-ratio:2){#logo{background:url(//www.google.com/images/branding/googlelogo/2x/googlelogo_color_150x54dp.png) no-repeat;-webkit-background-size:100% 100%}}#logo{display:inline-block;height:54px;width:150px}
      </style>
      <a href=//www.google.com/><span id=logo aria-label=Google></span></a>
      <p><b>404.</b> <ins>That's an error.</ins>
      <p>The requested URL <code>/v1beta1/projects/jetpack-dev/locations/us-east1/clusters/projects/jetpack-dev/locations/us-east1/clusters/dev-gcp-us-east1/nodePools?alt=json&prettyPrint=false</code> was not found on this server.  <ins>That's all we know.</ins>

Here’s the resource definition:

const nodepool = new gcp.container.NodePool(
      `${name}-pool2`,
      {
        cluster: cluster.id,
        location: config.require("region"),
        nodeCount: 1,
        autoscaling: {
          minNodeCount: 1,
          maxNodeCount: 10,
        },
        nodeConfig: {
          serviceAccount: serviceAccount.email,
          oauthScopes: ["<https://www.googleapis.com/auth/cloud-platform>"],
          machineType: "e2-standard-8",
          imageType: "UBUNTU",
        }
      },
      {
        provider: gcpProvider
      }
  );

am i missing something silly/simple here?