Hello!

Hey everyone, I'm getting following error after upgrading to 2.1: `error: could not load plugin for digitalocean provider 'urn😛ulumi:staging::wegroup:😛ulumi:providers:digitalocean::default_2_1_0_alpha_1586903880': no resource plugin 'digitalocean-v2.1.0-alpha.1586903880' found in the workspace or on your $PATH, install the plugin using `pulumi plugin install resource digitalocean v2.1.0-alpha.1586903880`` Now installing with above command didn't work:

error: [resource plugin digitalocean-2.1.0-alpha.1586903880] downloading from <https://api.pulumi.com/releases/plugins>: 404 HTTP error fetching plugin from <https://api.pulumi.com/releases/plugins/pulumi-resource-digitalocean-v2.1.0-alpha.1586903880-linux-amd64.tar.gz>

How do i fix this? Preferrably i'd actually use

pulumi plugin install resource digitalocean 2.3.0

if possible.

SOLUTION to my own problem above

pulumi plugin install resource digitalocean 2.3.0

#You can set the environment variable PULUMI_ENABLE_LEGACY_PLUGIN_SEARCH=1 to get unblocked and load plugins exactly as before.

export PULUMI_ENABLE_LEGACY_PLUGIN_SEARCH=1

Then I manually fixed Providers in stack.json aften export, then import

Hi team, does Pulumi support

<http://networking.gke.io/v1beta2|networking.gke.io/v1beta2>

?

Hi team, Can someone explain how I can create a 'Modify' policy assignment for enforcing tag creation please using the InBuilt Microsoft policy definition? When I try and do this through the Pulumi API I get an error from the Azure CLI about requiring the --assign-identity option on the command? There does not appear to be a way to add this through the Pulumi API? Many thanks.

Hi Team, I'm wondering if I can call Azure CLI command in the same scope of Pulumi script so I can pass generated names for resource group etc to the CLI command.

so I have this situation, I exported ACM certificates from one stack and I am referencing them into another, problem in that, that I am also using some of the data to build resource names in the latest stack. The name does not resolve to what I want and I end up with a resource named

<pulumi.output.Output object at 0x7f662973a100>-elb-ssl-listener

is it possible to reference outputs into resources names?

Hey , I am having issues with doing npm install in a linux box I get the following

verbose npm  v6.14.4
293 error code ELIFECYCLE
294 error syscall spawn
295 error file sh
296 error errno ENOENT
297 error deasync@0.1.19 install: `node ./build.js`
297 error spawn ENOENT
298 error Failed at the deasync@0.1.19 install script.
298 error This is probably not a problem with npm. There is likely additional logging output above.

I use pulumi 2 , I tried with node version 12 and 14 , with same outcome , All of this worked fine in my Mac , Any idea about this ?

When using the C# SDK : Is it possible to create a Blob from a byte[] or stream? Or can it only be created from local-file?

Why would pulumi be trying to delete my cluster when I deploy a new service? The cluster was created in crosswalk from an existing cluster that was imported and flagged with protected. We have a lot running on the cluster that is not managed by pulumi, so it is not possible to have it delete the cluster to deploy a new service. Any ideas where to look for what is causing the "replace" on that cluster resource?

Posted this message in #aws, but there seems to be a lot more activity here: Is there a way to pass in an existing 

<http://aws.lb|aws.lb>.LoadBalancer

 to a new 

<http://awsx.lb|awsx.lb>.ApplicationLoadBalancer

? I am using the typescript package currently. I want to take advantage of the features of aws crosswalk, but it's import that I can use an imported resource of an ALB that already exists in my amazon account.  For all the other crosswalk resources, I have used the pattern of creating a non crosswalk resource using the 

import

 option and then passing that in as the argument to create the crosswalk resource.  Am I missing something here with the load balancer? As far as I can tell, it will always create a new load balancer and there is no way to pass in an existing one. To draw a comparison to other resources, when creating a crosswalk cluster, you can pass in an existing aws cluster. If it exists, it will get the cluster and use it, if it doesn't it creates a new cluster.  Looking at the source for the load balancer, it seems to always create one no matter what. Cluster Implementation https://github.com/pulumi/pulumi-awsx/blob/6e41506897a3d7bf3985beb8ecdc596638047699/nodejs/awsx/ecs/cluster.ts#L49 Load Balancer Implementation https://github.com/pulumi/pulumi-awsx/blob/6e41506897a3d7bf3985beb8ecdc596638047699/nodejs/awsx/lb/loadBalancer.ts#L42

Hi guys, first time here sorry for coming straight up with a question. I used to get my cloud-init files pre-formatted with python to initialise my swarm and on the latest update it doesn't work anymore. I'm just wondering if it's a bug of if people have a better way to do this hence the drop of support for this. What I was doing is returning the ScaleSet in an Output.all, but now it just never creates the scalesets anymore. Here is some pseudo code of what I'm doing:

def get_cloud_init(param1, param2, param3):
    with open('cloud-init.sh') as f:
        return f.read().format(param1=param1, param2=param2, param3=param3)

def swarm_scaleset(role, count=1, instance_type=None):
    return pulumi.Output.all(param1, param2, param3).apply(
        lambda args: az.compute.ScaleSet(
            ...
            os_profile={
                ...
                'custom_data': get_cloud_init(*args),
                ...
            },
            ...
        )
    )

managers = swarm_scaleset('manager', 3, 'Standard_B1ms')
workers = swarm_scaleset('worker', 10, 'Standard_B1ms')

How do people handle this scenario usually?

Ok so answer to my own question, something that didn't work before but works perfectly now is to use the output in the custom data, like so:

def get_cloud_init(param1, param2, param3):
    with open('cloud-init.sh') as f:
        return f.read().format(param1=param1, param2=param2, param3=param3)
def swarm_scaleset(role, count=1, instance_type=None):
    return az.compute.ScaleSet(
        ...
        os_profile={
            ...
            'custom_data': pulumi.Output.all(param1, param2, param3).apply(
                lambda args: get_cloud_init(*args)
            )
            ...
        },
        ...
    )

managers = swarm_scaleset('manager', 3, 'Standard_B1ms')
workers = swarm_scaleset('worker', 10, 'Standard_B1ms')

I'm testing it at the moment and it seems to work ok, I'll test it on a fresh install soon (which was the problem before)

This message was deleted.

hello, Do you know if it is possible in pulumi portal to hide Values of resources created. I don't really want some users to see the password.

I have a k8s cluster, and I saved another k8s cluster’s kubeconfig in the first k8s cluster as secret. I want to build a k8s provider from the kubeconfig secret.

export const secret = k8s.core.v1.Secret.get("kubeconfig", "admin/kubeconfig-for-admin");
export const k8sProvider = new k8s.Provider("new-cluster", {
    kubeconfig: secret.stringData["kubeconfig"],
});

But the

k8sProvider

does not work as expected, I couldn’t see the kubeconfig field in it. Does anyone know why it is that? I’m pretty sure the kubeconfig was stored as base64 string in the

admin/kubeconfig-for-admin

.

Upgrade Free Plan to Team Starter - Is it possible to do this without creating a new organization?

Hi community, a new one here! 🙂 I'm a full stack-dev working for a social enterprise named Kinder.world - we have just started to use Pulumi recently

So here is my first question: feel free to direct me to the corresponding docs or FAQ item if I missed something 🙂 What is your best practice to manage / organise stacks and the code? Specifically: I created a script which manage my dns zones in AWS Route53. I also saved this to a git repo, done. Now my next thing would be to create another script to manage docker containers in ECS. But where should I put this? I am afraid I will lock myself if I create everything in the same stack / repo, because when I intend to delete some portion of my resources (let’s say ECS this case) with `pulumi destroy`I would kill everything (including my dns zones). Do you usually create new repo / stack for each resources?

If I use the local state backend with

pulumi login file://<path>

, does

<path>

represent an absolute path, or can I use a relative one too? If so, how? I tried

file:./state

, but I only get

.pulumi

folder created in my current folder, not in a

state

subfolder.

pulumi up

is getting stuck at the preview stage, even if the pulumi program is empty:

$ pulumi up
Previewing update (dev):
     Type                 Name               Plan     
     pulumi:pulumi:Stack  empirica-base-dev           
 
System Messages
  ^C received; cancelling. If you would like to terminate immediately, press ^C again.
  ^C received; terminating
  ^C received; terminating

It won't even terminate with Ctrl+C. How do I troubleshoot this? I did try reinstalling pulumi. Also tried creating a new stack. Still fails.

We are trying to deploy multiple pulumi stacks in parallel while there are stack references defined among those stacks. We defined internal guidelines to make sure we never make pulumi changes that change the value of the pulumi resources that are being referenced by another stack, which means during the paralel build of a set of pulumi stacks, it doesn’t matter if one stack is referencing an older state of another stack or a newer state. But we are wondering if pulumi actually support reading the stack reference while that stack is being deployed by another pulumi process?

should pulumi work on node v 13.2?

i can’t even get the basic “getting started” with AWS to deploy

Hi all! Pulumi n00b here, but I'm moving right along. I basically have an entire vSphere datacenter automated with Python and Pulumi. The only problem that I'm seeing is vSphere HA is trying to configure on the hypervisors before datastores have been created and mounted and thus failing. I'm not seeing a

dependsOn

flag in

opts=

for the vSphere cluster resource. Looking through the docs that's where I see the flag but I don't see it in vSphere.

vSphere Cluster HA error.

Hello All. Is there any way we can provision the node while it's creating by Pulumi ? I am referring Terraform provisioner here.

• I get the same errors during the initial deployment as well as updates. • Other resources are consistently deploying without issues • Pulumi fails on the exception, then AWS successfully deploys the Lambda, leaving Pulumi without the correct state • Deployments using the same stack, branch, and AWS credentials from other machines/connections do not face the same error • I started having this issue with an older 1.x version and have since updated to 2.1.0. • There was a thread started a few days ago that looks like the same issue. https://pulumi-community.slack.com/archives/CJ909TL6P/p1588234271145800

deleteBeforeReplace

doesn't solve the issue. Here is the index.js code that I'm producing the error with

const aws = require( '@pulumi/aws' );
const awsx = require( '@pulumi/awsx' );

const api = new awsx.apigateway.API( 'some-name', {
	routes: [ {
		path: '/something',
		method: 'POST',
		eventHandler: new aws.lambda.CallbackFunction( 'lambda-test', {
			memorySize: 128,
			callback: ( event ) => {
				console.log( event );
			},
			description: 'Some description',
		} ),
	} ],
} );

return {
	url: api.url,
};

Hi all. As of last Friday, I've started getting an error anytime I try to create or update a Lambda function.

Error creating Lambda function: ResourceConflictException: Function already exist

Here are relevant log entries from a Pulumi update that shows a ResourceConflictException happens 5 seconds before the successful deployment, possibly suggesting an issue with timeouts and retries.

@timestamp,@message
2020-05-05 18: 07: 15.676, "{""eventVersion"":""1.05"",""userIdentity"":{""type"":""IAMUser"",""principalId"":""AIDA3SNA767QOR3RN3I4Y"",""arn"":""arn:aws:iam::795443460064:user/chad.ort.snopes.local"",""accountId"":""795443460064"",""accessKeyId"":""AKIA3SNA767QJLIPDJSB"",""userName"":""chad.ort.snopes.local""},""eventTime"":""2020-05-05T17:50:10Z"",""eventSource"":""<http://lambda.amazonaws.com|lambda.amazonaws.com>"",""eventName"":""CreateFunction20150331"",""awsRegion"":""us-west-2"",""sourceIPAddress"":""97.114.75.236"",""userAgent"":""aws-sdk-go/1.29.7 (go1.13.8; darwin; amd64) APN/1.0 HashiCorp/1.0 Terraform/0.11+compatible (+<https://www.terraform.io>)"",""requestParameters"":{""functionName"":""lambda-test-2d7ed19"",""runtime"":""nodejs12.x"",""role"":""arn:aws:iam::795443460064:role/lambda-test-f532b55"",""handler"":""__index.handler"",""code"":{},""description"":""write events to queue and return 200"",""timeout"":180,""memorySize"":128,""publish"":false,""environment"":{}},""responseElements"":{""functionName"":""lambda-test-2d7ed19"",""functionArn"":""arn:aws:lambda:us-west-2:795443460064:function:lambda-test-2d7ed19"",""runtime"":""nodejs12.x"",""role"":""arn:aws:iam::795443460064:role/lambda-test-f532b55"",""handler"":""__index.handler"",""codeSize"":7957025,""description"":""write events to queue and return 200"",""timeout"":180,""memorySize"":128,""lastModified"":""2020-05-05T17:50:10.334+0000"",""codeSha256"":""Hcc9msmvBw+tYRsWLEEf1wItAJ6UEbRtCXg6QwD49ds="",""version"":""$LATEST"",""environment"":{},""tracingConfig"":{""mode"":""PassThrough""},""revisionId"":""275fde3f-46de-4790-bd08-90f2be49e309"",""state"":""Active"",""lastUpdateStatus"":""Successful""},""requestID"":""37d15659-0d93-4586-80ba-dfce76c82a94"",""eventID"":""47ff845a-105f-4d51-a06b-5c82bed05e57"",""eventType"":""AwsApiCall"",""recipientAccountId"":""795443460064""}"
2020-05-05 18: 07:10.282, "{""eventVersion"":""1.05"",""userIdentity"":{""type"":""IAMUser"",""principalId"":""AIDA3SNA767QOR3RN3I4Y"",""arn"":""arn:aws:iam::795443460064:user/chad.ort.snopes.local"",""accountId"":""795443460064"",""accessKeyId"":""AKIA3SNA767QJLIPDJSB"",""userName"":""chad.ort.snopes.local""},""eventTime"":""2020-05-05T17:51:04Z"",""eventSource"":""<http://lambda.amazonaws.com|lambda.amazonaws.com>"",""eventName"":""CreateFunction20150331"",""awsRegion"":""us-west-2"",""sourceIPAddress"":""97.114.75.236"",""userAgent"":""aws-sdk-go/1.29.7 (go1.13.8; darwin; amd64) APN/1.0 HashiCorp/1.0 Terraform/0.11+compatible (+<https://www.terraform.io>)"",""errorCode"":""ResourceConflictException"",""errorMessage"":""Function already exist: lambda-test-2d7ed19"",""requestParameters"":{""functionName"":""lambda-test-2d7ed19"",""runtime"":""nodejs12.x"",""role"":""arn:aws:iam::795443460064:role/lambda-test-f532b55"",""handler"":""__index.handler"",""code"":{},""description"":""write events to queue and return 200"",""timeout"":180,""memorySize"":128,""publish"":false,""environment"":{}},""responseElements"":null,""requestID"":""6f0ea757-b48e-4f43-8de2-0d92be3bd2c3"",""eventID"":""a3e9e0ac-643a-41e4-acb4-e26330d9c213"",""eventType"":""AwsApiCall"",""recipientAccountId"":""795443460064""}"

Additional known info