Is there any easy way to search the release notes to see when a certain functionality was added?

Hi dear community. Thank you so much for so nice product pulumi. My question around Azure Key #Vault. I already have Vault on my Azure account. I want to create a new Azure Function with SystemAssigned Identity and to add KeyVaultAccessPolicy for existed Vault. Is it possible to do in a new pulumi stack Pulumi.AzureNative C#?

Hi everyone! I've been looking for a way to create a pulumi provider plugin, in order to manage an internal resource service from my organisation (mainly the

create

,

delete

,

update

operations for that service (it is a simple CRUD API for managing a single internal resource)). The important part is that we want developers there to be able to import the plugin from a package manager, and then interact with our custom resource service without any hurdle. I've found 2 or 3 solutions online for this use case so far: 1. Pulumi Packages 2. Dynamic Providers In the last days, I tried to clone the TypeScript component package boilerplate and added an

update

member in the provider class. However, after compiling the code, only the

construct

member seems to be taken into consideration when using

pulumi up

or

pulumi preview

, which is not enabling me to support the CRUD nature of our internal service. I've found on Github multiple classes implementing the

pulumi.ProviderResource

interface, but in all of them, only the

construct

member is defined (i.e. not the

update

member), which makes me think this is not the right tool for my use case. We're trying to move away from Terraform, so the bridge solution described in the Packages documentation page doesn't seem appropriate either. I've also considered using a Dynamic Provider instead of the former TypeScript boilerplate. My idea was to simply put the classes implementing the

pulumi.dynamic.ResourceProvider

and

pulumi.dynamic.Resource

interfaces in a package manager. I wonder whether there are any major issue with this approach, other than the source code not scaling to more than one language (we would prefer to support more languages than just TypeScript, but it is not a hard requirement). What is the best way to support our custom CRUD service? I have listed some possible directions above, but I'm lacking pointers. I'm not sure why, but there doesn't seem to exist a lot of documentation about this topic online. Any help would be very appreciated! Also, if I am unaware of a more suitable solution for this case, please don't hesitate to let me know.

Hey, Pulumi people! Sorry for posting here so often, I’m really deep in the process of switching our infra from tf to Pulumi. Hope once it’s doen, things will stabilize 🙂 My question for today would be this: https://github.com/pulumi/pulumi-eks/issues/178 I think I’m running into the same issue with my

eks.Cluster

- I created it about a week ago or so. Things were fine for a while, but then something (default AMI id I guess) changed and produced a diff for Pulumi. Now if I try to

pulumi up

it fails saying it’s unable to delete an old Launch Configuration because it’s still attached to an ASG (which is true). I’m not sure what exactly went wrong, there were no interrupted updates or anything. I believe it’s just doing it in the wrong order, as I see new Launch Configurations are already created, they’re just not associated with an ASG yet. I think it should first attach the new configs and then delete the old ones, not vice versa. Anyway, my real question is what’s the best way out of this situation? Should I manually edit the state? I’m not quite sure how would I edit it though as these things are somewhat entangled. I’ve attached a screenshot of the error I’m getting as well as the code I’m using to create the cluster. Thanks for any help!

Yesterday I had a fully operational stack. Then today I tried to re-import an Azure resource group with

pulumi import

that was protected. Now when I do

pulumi up

it gives an error saying that the stack itself is a duplicate, and I can't get it back to a working state.

pulumi:pulumi:Stack (PulumiArm-hco):
    error: Duplicate resource URN 'urn:pulumi:hco::PulumiArm::pulumi:pulumi:Stack::PulumiArm-hco'; try giving it a unique name

Hello everyone. Is there a way to run a block of code just if X and Y resource was updated in a

pulumi up

?

pulumi.output.Unknown 😞 When change a instance of one region to another, the instance.name is getting pulumi.output.Unknown inside diff()

I have a case where I need to download an OpenAPI specification from GCP and then put that into a container. To do that I'm using a

DownloadFileInputs

. However, I have to pass an auth header which changes over time and the destination file for the download is a

tempfile

since I just need it temporarily. As a result Pulumi thinks that resource has changed and needs to be updated on each run. Is there a way to tell it to ignore certain aspects of the

DownloadFileInputs

like the header and the dest file?

Is there any work on developing a "bare-metal" mode for Pulumi? I'm very much in favor of using a real programming language to set up systems, but I don't like to use cloud services beyond hosting. It would be nice if Pulumi provided, as a library, code to launch and maintain self-hosted databases, proxies, etc, rather than just clients for cloud APIs. Something that could be used as an alternative to Ansible. Or are there any alternatives to Pulumi that support such a "bare-metal" mode?

Hello, is there anyone please who know how to set environment vars in pulumi with python for a lambda function, this information is NOT covered even one time in the documentation. Is it a dictionary {key:value} .

I'm having some trouble with resource creation ordering. I'm using the Docker provider to create an image that gets used by a Kubernetes Deployment. However, they both start creating at the same time and, of course, the deployment misses the image that isn't already built. I've tried using dependsOn and parent to no good. Also, when the image gets changed, the Deployment doesn't get replaced/recreated. How do I troubleshoot this?

Here's a thought that's probably showed up a million times before - but just in case: What about making something like

pulumi adopt

- functions like preview/refresh+import, but will preview all resources, and check if it might exist in the target, and if it does (and not in stack), import it. Alternatively, give an option on a failed

pulumi up

to automatically `import`resources into the stack that fail with the error

...already exists

- should be fairly cleear/standard on quite a few providers.

Hey Friends, There is a way to use pulumi to run ansible, some sort of provider for it? if not, is it in the road map?

Guys where I can read about packages Pulumi.Azure Pulumi.AzureNextGen Pulumi.AzureNative What the difference between them?

Does anyone know how to set backups for EFS? I've been through the pulumi docs and can't seem to find an option to do this.

Hello! Did anyone try to use ConfigGroup? For me, it creates empty CRDs from the files I specify...

Is pulumi down atm?

I'm getting 500 errors when doing

update

Ok, what the h**l. Suddenly

pulumi up

fails for me because Pulumi insists it has to replace all Kubernetes namespaces but when it tries to do that it fails since it apparently tries to create a new namespace with equal name first (since I have forced explicit names for a good reason) and that naturally won't work. Digged into the diff and it shows this

[provider: urn:pulumi:dev::my-project::pulumi:providers:kubernetes::k8s-provider::efaab349-6f4f-42ff-a607-ee6ab55cbb61 => urn:pulumi:dev::my-project::pulumi:providers:kubernetes::default_3_1_2::7b6466de-7864-49f9-8c33-0ece6217519a]

Which makes absolutely no sense to me. That is the only thing it is trying to change. This is 100% Pulumi internal stuff, apparently for some reason the provider has changed?

Can anyone share release plan? Looks like typescript sdk is not updated. I am getting exceptions like - ‘customEmailSender’ does not exist in type ‘Input<UserPoolLambdaConfig>’ (AWS)

Are pulumi integration tests compatible with v3? The doc examples are using

<http://github.com/pulumi/pulumi/pkg/v2/testing/integration|github.com/pulumi/pulumi/pkg/v2/testing/integration>

. When I add that package, go mod also adds these two indirect dependencies

<http://opkg.in/airbrake/gobrake.v2|opkg.in/airbrake/gobrake.v2> v2.0.9 // indirect
<http://gopkg.in/gemnasium/logrus-airbrake-hook.v2|gopkg.in/gemnasium/logrus-airbrake-hook.v2> v2.1.2 // indirect

Then, when I run

go test .

, I get the following error message

go test .                                                                                                                                                                                             [.]
panic: proto: duplicate enum registered: pulumirpc.EnforcementLevel

goroutine 1 [running]:
<http://github.com/golang/protobuf/proto.RegisterEnum(0x187e661|github.com/golang/protobuf/proto.RegisterEnum(0x187e661>, 0x1a, 0xc0005fbe60, 0xc0005fbe90)
        /home/vscode/go/pkg/mod/github.com/golang/protobuf@v1.4.3/proto/registry.go:104 +0x11f
<http://github.com/pulumi/pulumi/sdk/v3/proto/go.init.0()|github.com/pulumi/pulumi/sdk/v3/proto/go.init.0()>
        /home/vscode/go/pkg/mod/github.com/pulumi/pulumi/sdk/v3@v3.5.1/proto/go/analyzer.pb.go:963 +0x52
FAIL    <http://github.com/relativityone/r1-compute-infra/pkg/test|github.com/relativityone/r1-compute-infra/pkg/test>      0.027s
FAIL

Pricing question: if we sign up and pay for the year, then need to increase seats/users in a couple of months how does it work?

hey y’all, does anyone know why passing

-y

does not auto-accept the prompt when a stack doesn’t exist?

I've started working on a native pulumi provider package for an internal service at my company. Everything works fine, except for the fact that I can't get the

Update

function to be called when updating a resource instance. Any idea of how to turn off the delete -> create behaviour?

I keep having issues with projects and stack references. One stack deploys k8s clusters, then several stacks and environments use that stack to deploy on the clusters. As we are still finetuning the cluster setup, every now and then the clusters (or one of them) need to be recreated. At that point, all referencing stuff deployed on these clusters starts freaking out. I know i can just remove the stacks themselves, but that would cause me to have to redo the configs for dozens of stacks. Either our setup is bad, or i need either

pulumi destroy --if-failed-just-delete-from-stack

or a script that can “deep” delete everything from the stack export that depends on the stack reference. Anyone have such a such a script by any chance?

We keep hitting issues with AKS and Pulumi. Namely, when we try to update properties on existing AKS clusters (managed by Pulumi), we often get into error cases where we end up having to manually edit our stack. Here are some examples: We are unable to update the vm size. pulumi up fails and we have to manually delete the old AKS cluster, edit the stack and then run pulumi up to create the new cluster. Updating maCount on spot instance agent pools. Here’s the error we’re seeing:

azure-native:containerservice:AgentPool (dg-gpuspot-agentpool-cpu-staging-dev):
error: Code="PropertyChangeNotAllowed" Message="Changing property 'properties.nodeTaints' is not allowed." Target="properties.nodeTaints"

We weren’t trying to update the node taints. It seems like Pulumi knows it was a change to maxCount:

~  azure-native:containerservice:AgentPool dg-gpuspot-agentpool-cpu-staging-dev updating [diff: ~maxCount]; error: Code="PropertyChangeNotAllowed" Message="Changing property 'properties.nodeTaints' is not allowed." Target="properties.nodeTaints"

 ~  azure-native:containerservice:AgentPool dg-gpuspot-agentpool-cpu-staging-dev **updating failed** [diff: ~maxCount]; error: Code="PropertyChangeNotAllowed" Message="Changing property 'properties.nodeTaints' is not allowed." Target="properties.nodeTaints"

Taking a look at the stack output for this resource, I think the issue is that Pulumi is trying to remove the taints that Azure automatically adds to spot node pools. In this case we haven’t been able to get this to work even after editing the stack.

{
                "urn": "urn:pulumi:spark-staging::spark-deployment::azure-native:containerservice:AgentPool::dg-gpuspot-agentpool-cpu-staging-dev",
                "custom": true,
                "id": "/subscriptions/a8c3fdb1-94c2-4db4-bc18-470696fa4bd4/resourcegroups/cp-staging/providers/Microsoft.ContainerService/managedClusters/dg-spark-kubernetescluster-cpu-staging-dev/agentPools/gpuspot",
                "type": "azure-native:containerservice:AgentPool",
                "inputs": {
                    "agentPoolName": "gpuspot",
                    "count": 1,
                    "enableAutoScaling": true,
                    "maxCount": 6,
                    "minCount": 0,
                    "mode": "User",
                    "nodeTaints": [
                        "sku=gpu:NoSchedule"
                    ],
                    "resourceGroupName": "cp-staging",
                    "resourceName": "dg-spark-kubernetescluster-cpu-staging-dev",
                    "scaleSetPriority": "Spot",
                    "spotMaxPrice": -1,
                    "type": "VirtualMachineScaleSets",
                    "vmSize": "Standard_NC8as_T4_v3",
                    "vnetSubnetID": "/subscriptions/a8c3fdb1-94c2-4db4-bc18-470696fa4bd4/resourceGroups/cp-staging/providers/Microsoft.Network/virtualNetworks/dg-spark-vnet-cpu-staging-dev/subnets/default"
                },
                "outputs": {
                    "__inputs": {
                        "4dabf18193072939515e22adb298388d": "1b47061264138c4ac30d75fd1eb44270",
                        "ciphertext": "redacted"
                    },
                    "count": 1,
                    "enableAutoScaling": true,
                    "enableFIPS": false,
                    "id": "/subscriptions/a8c3fdb1-94c2-4db4-bc18-470696fa4bd4/resourcegroups/cp-staging/providers/Microsoft.ContainerService/managedClusters/dg-spark-kubernetescluster-cpu-staging-dev/agentPools/gpuspot",
                    "kubeletDiskType": "OS",
                    "maxCount": 6,
                    "maxPods": 110,
                    "minCount": 0,
                    "mode": "User",
                    "name": "gpuspot",
                    "nodeImageVersion": "AKSUbuntu-1804gen2containerd-2021.06.02",
                    "nodeLabels": {
                        "<http://kubernetes.azure.com/scalesetpriority|kubernetes.azure.com/scalesetpriority>": "spot"
                    },
                    "nodeTaints": [
                        "sku=gpu:NoSchedule",
                        "<http://kubernetes.azure.com/scalesetpriority=spot:NoSchedule|kubernetes.azure.com/scalesetpriority=spot:NoSchedule>"
                    ],
                    "orchestratorVersion": "1.19.11",
                    "osDiskSizeGB": 128,
                    "osDiskType": "Ephemeral",
                    "osSKU": "Ubuntu",
                    "osType": "Linux",
                    "powerState": {
                        "code": "Running"
                    },
                    "provisioningState": "Succeeded",
                    "scaleSetEvictionPolicy": "Delete",
                    "scaleSetPriority": "Spot",
                    "spotMaxPrice": -1,
                    "type": "VirtualMachineScaleSets",
                    "vmSize": "Standard_NC8as_T4_v3",
                    "vnetSubnetID": "/subscriptions/a8c3fdb1-94c2-4db4-bc18-470696fa4bd4/resourceGroups/cp-staging/providers/Microsoft.Network/virtualNetworks/dg-spark-vnet-cpu-staging-dev/subnets/default"

I asked the other day about where your Pulumi code should live in relation to your code repo, and there seemed to be a lot of consensus around putting it in

/infra

(see conversation here). Now, I’m following a tutorial that covers using separate projects for building a Docker image and pushing it to my cloud provider of choice: https://www.pulumi.com/docs/tutorials/gcp/gcp-ts-docker-gcr-cloudrun/ In this case, would it make sense to have two separate Pulumi folders? (

/build

and

/deploy

or something like that) Or should I always be building and deploying in a single step? I’m coming at this with some experience using Docker and docker-compose, so I’m used to building, pushing to a registry, and then pulling the image as three separate steps.

how do you declare an implicit dependency between resources when no explicit output dependency exists?