Hello, just getting started on the Slack here, we have a question with @colossal-camera-57941 about running nodeJs task on aws from an image ( using .fromFunction ); we’re not sure how to import others npm packages into this function. Is it here the right place to ask for that?

Is it possible in pulumi to create a temporary resource ? Consider a situation where you need to provision a resource that is useful only during provisioning of another resource. How to deal with that? Example situation: I want to provision some "state" into a persistent volume that is later used by some containers. In order to provision that data I'd like to 1) create temporary EC2 instance, 2) attach and mount that volume to that ec2 instance 3) run some scripts that provision some data 4) detach volume & delete temporary EC2 instance

A general question. If you do apply on a property of a resource to use that as input to another resource, when will the apply resolve? Will it resolve when the property has a value or will it resolve when the resource is ready? If it is the former, what is the recommended way of running some code after a resource is ready to calculate the input to another resource?

Hi, Got a question : i want to deploy on my gcloud cluster a deployment using an online yaml file . The only way i found on your documentation is to use Kubernetes.yaml.Configfile, but it use the default kubectl config file and not my current provider, and their is no way to pass the provider to the ConfigFile. Why? And do you have any Id why? Thanks, Gautier

Where is the "current stack" saved (for instance when running

pulumi stack select foo

)? How can I see which stack is currently selected?

Does the pulumi CLI support JSON output for the response? and more specifically, is there a way to do that in the managed GitHub action?

I've been using Pulumi in production for nearly a year - very happy with it. But our organization needs to refactor our applications we've built using Pulumi - in particular, we need to decompose some monolithic stacks down into some smaller ones. Is there a way to transfer resources between stacks without deleting them? We have some resources, i.e. databases and file storage, that we really do not want to delete / recreate from backup

Did pulumi 3.0 introduce any changes to unit testing related to resource reads? I've updated the

pulumi.runtime.setMocks

. I have some tests that work fine before updating, but after updating fail with an error like

failed to read resource #user 'test-user' [aws:dynamodb/table:Table]: req.getCustom is not a function

Hello! We use Rancher and I am listing the Rancher clusters in the Pulumi config file and looping over them to deploy a Helm chart. It looks like I am missing something as there are resource name collisions. I want the _release_name_ to be the same in both releases but simply applied to different clusters. I tried looking at the transformations stuff but I don't think I can update the resource_names with that. Any tips are appreciated!

I got an error when trying to import crawlers, it returns an error telling me that I must especify at least one target, but it alredy has the S3Target. Does anybody knows how to skip it?

Can all organizations have policy packs published? I'm getting a 409 error...

[409] This organization does not support Policy as Code.

Also, does policy as code support mono repos? I've deleted the generated package.json and added the dependency to my shared package.json, but I'm getting

Error: Cannot find module '/pulumi/projects/main/pulumi/policy-packs/localpolicies/package.json'

Related to above: policy packs don't use the creds in a resource's provider property. Is this something that could reasonably happen? I can raise an issue about it, if it's fixable.

Hi, curious why pulumi sets file permissions to 600 when running pulumi new?

Hi, I'm wondering if there is a way to set configuration values (secrets especially) from code using Pulumi's APIs? I know I can always invoke a shell command but that seems silly if there is a programmatic access to this somewhere. The use case in this regard would be to ask for initial users to be created into a system. Passwords are the important part here. Sure one can just generate those and print those out but in this case it would be useful to be able to type the preferred passwords in. Why I'm thinking using configuration mechanism with this is because this would allow checking if those have already been set or not when executing the code for the first time. If they are in remote state then this would apply over all use cases no matter the developer - meaning initial users don't get created several times.

Hey all! I'm trying to rollout gradually my cloud run service but with no success so far and I would love your advise:

const runningService = pulumi.output(
  gcp.cloudrun.getService(
    { name, location },
    {
      async: true,
    },
  ),
);
const service = new gcp.cloudrun.Service(
  name,
  {
    name,
    // autogenerateRevisionName: true,
    location,
    traffics: runningService.traffics,
    template: {
      metadata: {
        name: 'api-rolling-test3',
        annotations: {
          '<http://run.googleapis.com/vpc-access-connector|run.googleapis.com/vpc-access-connector>': vpcConnector.name,
          '<http://run.googleapis.com/vpc-access-egress|run.googleapis.com/vpc-access-egress>': 'private-ranges-only',
        },
      },
      spec: {
        serviceAccountName: serviceAccount.email,
        containers: [
          {
            image,
            resources: { limits: { cpu: '1', memory: '512Mi' } },
            envs: secrets,
          },
        ],
        containerConcurrency: 250,
      },
    },
  },
  { dependsOn: [...iamMembers, redis] },
);

Above is the service creation and then I want to update only the traffic property so I'm trying to create another service:

new gcp.cloudrun.Service(
  name,
  {
    name,
    location,
    traffics: [
      {
        revisionName: runningService.traffics[0].revisionName,
        percent: 99,
      },
      {
        revisionName: service.template.apply(
          (template) => template?.metadata.name || '',
        ),
        percent: 1,
      },
    ],
  },
  { dependsOn: [service] },
);

But it throws duplicate urn error 🥴

Hi everyone, would it be a valid Pulumi scenario to resize an existing Amazon EBS volume that was not created as part of Pulumi stack? It was created for an EC2 instance that use an Image from the Marketplace, volumes were provisioned automatically there and they are too small. Overall EC2 instance setup is managed by Pulumi though. Any suggestions welcomed :)

can I get some links toward any information regarding writing your own pulumi provider?

Is there a way to refer to an existing container image on the local host in order to, say, push it to a remote repository during a Pulumi run, but not build that image during the Pulumi run? https://www.pulumi.com/docs/reference/pkg/docker/image/ looks close, but seems to require the building of the image. I'd like to be able to decouple image building from infrastructure provisioning.

hey guys, does pulumi work with vmware tanzu?

just upgraded to 3.2 and now getting an error with saying it cant find an env var (but it's there):

root@6d65e624ef9c:/data/pulumi/infra/aws/environment/appsync# pulumi stack select appsync.e_stage.n_main.r_us-west-2
error: constructing secrets manager of type "passphrase": unable to find either `PULUMI_CONFIG_PASSPHRASE` or `PULUMI_CONFIG_PASSPHRASE_FILE` when trying to access the Passphrase Secrets Provider; please ensure one of these environment variables is set to allow the operation to continue

root@6d65e624ef9c:/data/pulumi/infra/aws/environment/appsync# env | grep PULUMI_CONFIG_PASSPHRASE
PULUMI_CONFIG_PASSPHRASE=

root@6d65e624ef9c:/data/pulumi/infra/aws/environment/appsync# pulumi version
v3.2.0

Hi, When I am running

pulumi up

, I was given this message

Previewing update (dev)                                                                                                                                                                          
                                                                                                                                                                                                 
View Live: <https://app.pulumi.com/zhouyu1800/documents_api/dev/previews/d3783c77-2df4-436a-a792-a9b8205c9be8>                                                                                     
                                                                                                                                                                                                 
     Type                 Name               Plan     Info                                                                                                                                       
     pulumi:pulumi:Stack  documents_api-dev                                                                                                                                                      
     └─ aws:iam:Role      documentsPost               1 error                                                                                                                                    
                                                                                                                                                                                                 
Diagnostics:                                                                                                                                                                                     
  aws:iam:Role (documentsPost):                                                                                                                                                                  
    error: AWS Account ID not allowed: 228886564947

But I never know that account.

The same AWS credential works on my other pulumi projects.

Can anyone help me debug this?

I've got a situation I've not seen before; I'm trying to install linkerd with pulumi with the helm chart -- I'm passing in the certificates as secrets from the pulumi config and interpolating them in the

values

section of the

k8s.helm.v2.chart

resource The issue is that every-time I run a pulumi up it looks like the secret values are changing in k8s and the checksums on the deployments are changing; any thoughts as to why?

Hi, I'm running into an issue using the Pulumi Github action and I'm not sure what is going wrong. Could somebody help me make sense of this? 🙏

[resource plugin gcp-5.0.0] installing
  
  Downloading plugin: 0 B / 34.41 MiB    0.00%
  Downloading plugin: 3.51 MiB / 34.41 MiB   10.19% 1s
  Downloading plugin: 10.03 MiB / 34.41 MiB   29.16%
  Downloading plugin: 15.23 MiB / 34.41 MiB   44.25%
  Downloading plugin: 20.62 MiB / 34.41 MiB   59.91%
  Downloading plugin: 25.93 MiB / 34.41 MiB   75.36%
  Downloading plugin: 31.06 MiB / 34.41 MiB   90.26%
  Downloading plugin: 34.41 MiB / 34.41 MiB  100.00% 1s
  
      pulumi:pulumi:Stack replayvalue-dev running 
      pulumi:providers:gcp default_5_2_0  error: no resource plugin 'gcp-v5.2.0' found in the workspace or on your $PATH, install the plugin using `pulumi plugin install resource gcp v5.2.0`
      pulumi:pulumi:Stack replayvalue-dev  
      pulumi:providers:gcp default_5_2_0  1 error
   
  Diagnostics:
    pulumi:providers:gcp (default_5_2_0):
      error: no resource plugin 'gcp-v5.2.0' found in the workspace or on your $PATH, install the plugin using `pulumi plugin install resource gcp v5.2.0`

Hello everyone, happy Friday… something happen on one of my

dev

stacks and become

dev*                                  n/a           n/a

I’m trying to import the backup from

dev.json.bak

but getting

error: could not deserialize deployment: unexpected end of JSON input

from `pulumi stack import --file dev-bkp.json`… is there a way to directly import the

bak

or something else beforehand should be done?… also

pulumi refresh

doesn’t do anything…

Getting

pulumi stack output

in a file using the Azure DevOps Pipeline task We need to do some post processing using the stack output on azure devops. I want to do this with a service connection to avoid having to worry about secrets. If I run pulumi using the azure CLI task I'm getting an error relating to connecting to the blob container that's used for the pulumi back end. This is notionally easy to fix, run

pulumi stack output --json

using the pulumi task (which I know will work because

pulumi up

works) capturing the output to a file that I can then feed into the powershell that does the things we can't currently do with pulumi. Except I can't capture the output 😢 Open to suggestions at this point (before I put a feature request in to add --output to the CLI)

Anyone knows if there is a known issue showing diffs properly in certain scenarios? Been trying to search for open issues but no success so far. I first thought it would be output/input related but it’s occurring also for values that are just plain strings 🤔 (using typescript, pulumi v2.24.1)