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?

I’m wondering what’s the reason for

pulumi state delete

to not support resource deletion if it has children. I’m trying to delete a

k8s.yaml.ConfigFile

, which subsequently expands into ~100 k8s resources and deleting them one by one manually is just not feasible..

When I run pulumi up for the first time it goes fine, but when I try again without any changes, I am getting the following error: error: Code="InUseSubnetCannotBeDeleted" Message="Subnet functions is in use by ***virtualNetworks/***/subnets/functions/serviceAssociationLinks/AppServiceLink and cannot be deleted. In order to delete the subnet, delete all the resources within the subnet. See aka.ms/deletesubnet." Details=[] Any suggestion is greatly appreciated!

hi all! i have encapsulated the logic for obtaining a viewer certificate for cloudfront (aws) into a function (note I'm returning it in the very first line):

function getViewerCertificate(
  customDomain: string | undefined,
  ... // other parameters
): pulumi.Input<aws.types.input.cloudfront.DistributionViewerCertificate> {
  if (!customDomain) {
    return {
      minimumProtocolVersion: 'TLSv1.1_2016',
      cloudfrontDefaultCertificate: true,
    }
  }

which I later call it (with

customDomain

set to

undefined

)

const viewerCertificate = getViewerCertificate(customDomain,...)

and use it:

const distributionArgs: aws.cloudfront.DistributionArgs = {enabled: true, aliases: customDomain ? [customDomain] : [], viewerCertificate, ...}

and after running the

update

command with automation api this change is detected on every deploy as an updated resource, taking a lot of time to complete the operation. I understand that pulumi should not detect this as a change. is this an expected behavior? it seems like a bug to me

Any way to easily edit a specific value in state? I have a

RandomUuid

value and everything is working correctly except it was in different value when it was applied to specific service and it stored it into it's database during initial startup. I would like to use that value and change it into Pulumi state so that it gets set correctly elsewhere but still keep the

RandomUuid

so that if and when a new env is setup with Pulumi configs it will get generated as it should

hello people! got a question about github callbacks. So we had a bash script that was doing sequential previews on PRs (just calling pulumi preview), with time we got more and more projects and this has become unsustainable; we then refactored a bit the bash script with a python version which now uses the automation API + some concurrency to speed things up. The issue tho, is that we are not getting callbacks on github with this new model, is this because we use the automation API?