@full-dress-10026 If you run

pulumi stack export

do you see that launch configuration listed?

https://azurecharts.com/ for those interested

When importing an app service plan resource on azure, I get the following warning:

=   └─ azure:appservice:Plan  dev                             import     [diff: +location,reserved,sku~kind,name]; 1 warn
Diagnostics:
  azure:appservice:Plan (dev):
    warning: inputs to import do not match the existing resource; importing this resource will fail

Is there a way to diff the current and preview state of apps? The details section gives me some info but it doesn’t present a diff (I’m guessing it might be due to casing Linux vs linux causing pulumi to think that the details do not match.) I have tried running with

-v=3

but did not help that much.

Just a general question. Scenario: I cannot run a successful

pulumi destroy

if the deployed stack contains a bucket with existing objects. I can easily delete such buckets with the AWS CLI (e.g.

aws s3 rb --force

<s3://my-bucket-with-objects>

). (I know this is an AWS restriction that we override with the

--force

flag). Question: Is there a way to tell pulumi to destroy bucket resources even if they have objects inside (and let it handle doing a forceful destroy of these buckets?). This is my ideal scenario instead of running special pre-destroy operations by hand.

is anyone here using pulumi in conjunction with spinnaker? Any thoughts on this combo?

Anyone using Pulumi for Azure data pipelines? Data factory based? API Gateways? Micro-stacks for deploying different parts of a pipeline?

Hey is this feature in the new update on 1.6.0

pulumi watch

How can I run a bunch of stacks with the same name? So I have a

log_setup

which setup's logging for AWS. They are all in there own named stack with the stack name of

log_setup

, if that makes sense! I want to be able to run them all at once. If possible.

https://aws.amazon.com/blogs/aws/new-application-load-balancer-simplifies-deployment-with-weighted-target-groups/ Is there an ETA for this being supported in Pulumi? I've been following a Terraform issue for many moons about other ALB routing rules that aren't supported yet https://github.com/terraform-providers/terraform-provider-aws/issues/8126 If that isn't available soon, are there any suggested approaches to scripting a workaround for being able to set these routing rules?

I’d like to try out the

pulumi up --target

option, however I am seeing that the preview is not limited to the targeted URN I provide. Is that expected? Will the targeting only affect the actual

up

once I approve it.

Technically Firestore is supported right? I see the Terraform provider, and the generated doc page...I have not seen a single example of anyone using this...anyone know?

Ahh interesting read on the Terraform GitHub page says I should probably be managing all my Firestore stuff from functions...yes that makes sense as I am doing 99% of that currently using Pulumi with GCP Functions...Well then, that's easy enough!

Anyone already deployed linkerd with pulumi? I guess, currently, the only way is to use the helm charts - from github issue (https://github.com/pulumi/pulumi/issues/99) I understand, there is no possibility yet to run (shell) commands within pulumi. Using the helm chart also involves some command line work, since you need to setup the certificates used by linkerd by yourself (https://linkerd.io/2/tasks/install-helm/). What's the suggested way to do this right now? Write a shell script that runs the commands and pulumi - this is the only thing that comes to my mind right now. Any advice is greatly appreciated.

Does pulumi support storageClass with

WaitForFirstConsumer

? When I make a PVC with Pulumi, pulumi hangs waiting for it to no longer be pending, which won’t happen unless the pulumi controller creates the pods that depend on that PVC.

When running the code below,

pulumi up

had to be run twice in order to create the resources. First time it creates the table and the second time it creates it the item inside the table.

import json
import pulumi
from pulumi_aws import dynamodb

table_default_name = dynamodb.Table(
    'pulumi-poc-test-table',
    hash_key='id',
    attributes=[
        {'name': 'id', 'type': 'S'}
    ],
    write_capacity=1,
    read_capacity=1
)

debug_object_1 = \
table_default_name.name.apply(lambda table_name: \
    dynamodb.TableItem(
        'test_item',
        hash_key='id',
        item=json.dumps({'id': {'S': 'yes'}}),
        table_name=table_name
    )
)

Yesterday, I noticed that the permalink for the s3 backend creates an expiring link to the state file, is possible to either toggle off the display of the permalink or set the permalink to not use an expiring link?

Hi, is it possible to get hold of the "host key" of an Azure Function App using pulumi dotnet? Have been looking around a bit and it seems that it's possible in ARM-templates at least, but recently added. browsing the nodejs-sdk led me to believe that there is a method called getHostKeys() there (https://github.com/pulumi/pulumi-azure/blob/814aeefbe707f94356a8f21fc35e192ce8633607/sdk/nodejs/appservice/zMixins.ts#L832), but cannot find in dotnet?

I'm having an issue that seems to happen only on the latest Pulumi version

1.6.0

. I have a stack reference and retrieve an output using

getOutputSync()

but the output becomes undefined. The same code works with version

1.5.2

. Still in version

1.6.0

, if I execute the following snippet I can see the whole output as expected

namespacesStack.outputs.apply(o => console.log(o));

. Anyone having the same issue?

Hi everyone, I am excited about the prospect of using Pulumi for my IaC. One question I have is have there been any thoughts about incorporating Pulumi into GitOps flows/operators? I am talking about something like Flux CD that will automatically apply and update your K8s clusters to stay consistent with what is in git, even automatically push changes when new images are detected, etc. Flux CD currently expects K8s yaml manifests or HelmRelease CRs, supported kustomize, etc.

how do i create stack from commandline?

pulumi stack select

gives an option

<create a new stack>

, would like to create without being interactive.

Hello, does anyone know how to convert

Output<String>

to

string

? for example

const eksClusterName = eksInfra.requireOutput("eksClusterName"); // This line returns Output<string>
pulumi.log.debug(eksClusterName) // How to let this line work?

Looks like EKS just introduced managed worker groups. How long until Pulumi supports this feature?

Takes a good long time for cloudfront distro's to finish updating, but pulumi up wants to wait for it. Is that the expected behavior?

Is there a way to get the current stack from the pulumi command quickly? The only one I know of is to 'pulumi stack ls' and get the one with the asterisk. I can also find the appropriate file in ~/.pulumi/workspaces/<dir>-<id>-workspace.json. But I'd prefer to use the command.

I'd like to include the current stack in my prompt.

I have a Kubernetes deployment with three replicas where one is leader and the other two are standby. The way this software works, the two standby pods never report as Ready; only the leader pod does. This is desirable, because this Deployment is fronted by a Service, and having the non-leader pods not report as Ready keeps them out of rotation in the Service load balancer. Is there a way to tell Pulumi, "this deployment is ready when one of the three pods is Ready?"

What is people's recommendation when moving from a large terraform base to pulumi? tf2pulumi is lacking tf 0.12 support, so I can't test its quality of output. I suspect it's going to be a rewrite from scratch?

Does Pulumi re-read your program between the preview and update steps?

If I have deleted an EKS cluster from the console, how do I get Pulumi to understand it has been deleted and to figure out what to do with all the deployments. Currently every deployment I have now fails to delete with this message:

error: unable to load schema information from the API server: Get <https://F7E1844F423B2899F4D9B934F2EFE568.yl4.us-west-2.eks.amazonaws.com/openapi/v2?timeout=32s>: dial tcp: lookup <http://F7E1844F423B2899F4D9B934F2EFE568.yl4.us-west-2.eks.amazonaws.com|F7E1844F423B2899F4D9B934F2EFE568.yl4.us-west-2.eks.amazonaws.com>: no such host

I would honestly be fine with destroying the whole stack but that can't be done because I can't get past this error.