Do you guys have templates for making a pulumi provider (i.e. something that is not a TF provider)?

Hello people, I'm running into this weird issue with AKS. The nodepool gets re-created any time I do

pulumi up

, which now makes the deployment take so long. This is what my cluster looks like:

const k8sCluster = new azure.containerservice.KubernetesCluster(config.clusterName, {
    resourceGroupName: resourceGroup.name,
    location: resourceGroup.location,   
    name: config.clusterName,
    agentPoolProfiles: [{
        name: "nodepool1",
        count: config.nodeCount,
        vmSize: config.nodeSize,
        osType: "Linux"
    }],
    dnsPrefix: `${pulumi.getStack()}-kube`,
    servicePrincipal: {
        clientId: app.applicationId,
        clientSecret: spPassword
    },
    tags: {
        environment: config.env,
    },
}, { dependsOn: [app, adSpPassword] });

And here is

pulumi up

in action:

Hello everyone 👋 here's the TL;DR I want to reuse existing kubernetes objects, instead of creating new ones, when applying pulumi More Detailed description of my Problem: I've got a little problem with the

import

of existing kuberenetes objects. What I thought It does: Now you can apply a new configuration over the very same kubernetes object What it does: It doesn't work, when there is a minor difference between the new and the existing configuration. Pulumi states that:

warning: inputs to import do not match the existing resource; importing this resource will fail

and fails with

error: inputs to import do not match the existing resource
error: update failed

What am I doing wrong here? I just want to update/reuse existing kubernetes ressources

Hey, is that a bug or by design?

m5d.2xlarge

Amazon Linux 2 AMI (HVM), SSD Volume Type

has by default 1x300GB SSD disk attached. When I create such instance using

new aws.ec2.Instance

everything is fine and ec2 instance is being provisioned with

/dev/nvme1n1    296G

volume. However, when I use exactly the same instance size and AMI (ami-0cc293023f983ed53), but create it in autoscaling group

new awsx.autoscaling.AutoScalingLaunchConfiguration

it has only ~55GB disk attached (

/dev/nvme1n1     53G

). Can you please help me to understand why and how I can increase disk size?

How is the launch configuration defined?

Loving Pulumi for Azure. Are there any plans to support IoT Central or Azure Digital Twin? #general #dotnet

Do cross-stack references support json, or is it simply key-val?

Hello everyone I'm running into an issue when using the output of a resource in an ARM template (Typescript). For example, this is the variables section of the ARM template

"variables": {
      "storageAccountName": config.appServicePlanStorageName,
      "storageAccountKey": appStorageAccount.primaryAccessKey,
      "location": config.location,
}

Note that

storageAccountKey

is gotten from another resource When the resource got deployed, the value of storageAccountKey was this:

Calling [toJSON] on an [Output<T>] is not supported.\\n\\nTo get the value of an Output as a JSON value or JSON string consider either:\\n    1: o.apply(v => v.toJSON())\\n    2: o.apply(v => JSON.stringify(v))\\n\\nSee <https://pulumi.io/help/outputs> for more details.\\nThis function may throw in a future version of @pulumi/pulumi.

I have tried

"storageAccountKey": appStorageAccount.primaryAccessKey.apply(v => JSON.stringify(v))

"storageAccountKey": pulumi.output(appStorageAccount.primaryAccessKey).apply(JSON.stringify)

`"storageAccountKey": pulumi.all([appStorageAccount.primaryAccessKey]).apply(([v]) => 

${v}

)`

Is anyone else having pulumi programs just break on 1.6.0 compared to 1.5.1

Re-apply "propagate resource inputs to resource state during preview, including first-class unknown values." The new set of changes have additional fixes to ensure backwards compatibility with earlier code. This allows the preview to better estimate the state of a resource after an update, including property values that were populated using defaults calculated by the provider. #3327

this change has bit us in two different repos

in one of them I get a real unhelpful traceback. I'm guessing somewhere of the 100 resources I make in this state, "name" isn't getting carried through since its a default from a provider.

we run .apply off of the properties of Outputs all the time

The primary use case for these APIs is to allow nested, properties with

known values to be accessed via the lifted property accessor even when

the containing property is not fully know. A common example of this

pattern is the

metadata.name

property of a Kubernetes

Namespace

object: while other properties of the

metadata

bag may be unknown,

name

is often known. These APIs allow

ns.metadata.name

to return a

known value in this case.

luckily theres a great git commit status message that listed exactly what my name was

In order to make ClusterRoleBindings of service accounts created with Pulumi we always have to do

def extract_resource_name(service_account_resource):
    return service_account_resource.metadata['name']

in order to get the fun -randombits Pulumi adds at the end when making the ClusterRoleBinding in python

I’m getting logged out of the Pulumi console frequently this morning, stack diffs are also intermittently showing

null is not an object (evaluating 'Object.keys(n)') DISMISS

Is there a way to suppress output from

pulumi plugin install

command when it is run from a package manager? Specifically, I'd like to omit the output:

[resource plugin aws-1.7.0] installing

Anything going on with this issue? https://github.com/pulumi/pulumi-kubernetes/issues/29

It'd be great to have a

pulumi render

command where I can get raw yaml out of my template

Are there any issues with pulumi at the moment. I'm running

pulumi preview

. It has now been running for > 10 minutes. I checked the previous time that it was run in activity history (17 Nov) and it completed in "seconds". Nothing has changed in the stack since then.

I'm using

awsx.ec2.Vpc

to manage VPCs. I have a VPC that previously didn't configure any NAT gateways. I just updated it with

numberofNatGateways: 2

to add some gateways but Pulumi doesn't detect the change. Is that a bug? If not, what am I doing wrong? And if so... how do I work around it?

i am having trouble after upgrading to the latest pulumi. started getting an error when using

aws.secretsmanager.getSecretVersion

where it retrieves an empty value.

I have 24 stacks in Pulumi now, I feel like thats some sort of achievement unlock or something!! lol

Hi @tall-librarian-49374, just quick question regarding to Azure AD B2C. How could we select difference Tenant when registering the application?

Hi I have one stack up and running with 2 k8 clusters with multiple helm charts deployed it. After the above stack is up, I tried to "pulumi up" on another different stack "in parallel" with same above configurations of helm charts, some of the charts are failing : "error: Plan apply failed: 2 errors occurred: * resource kibana-kibana was successfully created, but the Kubernetes API server reported that it failed to fully initialize or become live: 'kibana-kibana' timed out waiting to be Ready * Service was not allocated an IP address; does your cloud provider support this?" any idea on what is happening?

Hey friends, I used aws CloudFormation and found out some resources was not created with CloudFormation running successfully. I am supposed this is because CloudFormation is an asynchronous service. But anyway, Is it needed to verify aws resources are really created by pulumi up ?thanks.

Hey @quaint-artist-58613, why not amazon (web) console?

@quaint-artist-58613 You could also output resource IDs and check for them on the Amazon Web Console as @nutritious-airline-70839 suggested edit : or programmatically

@nutritious-airline-70839 because it is painful and impossible when there are hundred resources.

@lively-kangaroo-29833 The resources successfully created were shown in console but the ones failed to be created were not shown in console. So comparing console events are not working.

Hey! I have a general question 😉 I know pulumi is free and open-source. If my team (4ppl) wanted to use it for production setup - what all do I have to do to "unsubscribe" from the app?