in Kubernetes

I am thinking recreating the entire yml in Pulumi is probably a pain and not a good idea...

I guess I could use Helm...freaking hate helm though...

Hello All, I'm facing 2 issues when provision the Azure API Management: The provision is really take time and the Azure DevOps and Pulumi got timeout however, the resource eventually created on Azure. So the state on Azure and Pulumi are not matched. The second issue I got is not able to specify the Consumption sku in the setting. Please help if you have any solution. Thanks and Have a good day to all.

I'm looking for guidelines regarding how to work with

serverless

and

pulumi

side by side Serverless does a good job at providing code boilerplate and packaging functions but Pulumi far outclasses it when it comes to infrastructure provisioning. What's the best way to make those two work together ? Should I just add a "Managed By" tag to my resources depending on wether they were deployed by Serverless or Pulumi ? How do I automatically import in my Pulumi stack resources that were created by Serverless ? Is it better to not use Serverless's deployment features altogether ?

Does anyone know how to automatically tag everything on AWS created by pulumi so it becomes easy to find all resources created somewhere for staging or other stacks? And is there a way to set configs programatically?

I could find any resources on this, and I’ve asked before but no answer; How do you set configs and secrets programmatically. Using Typescript, looking at Config module, it has no setters. Technically what I need to do is to create stacks on the fly. The concept of pre-defined stacks seems like a broken idea. It’s useful for stuff like production. But not useful if you’re trying to deploy an isolated environment while reusing parts of existing resources. Say I want to reuse an existing ECR (AWS) but or an entire new stack. I would have to create a new stack create a new yaml file for the stack fill said yaml file with the configs and then apply said stack. Preferably, I would have just wanted to say

pulumi up new-stack-123 <bunch of env variables>

Is there a way to turn

pulumi.Output*<*string[]*>*

into a

pulumi.Input*<*string*>[]*

?

I’ve solved it like

let q  = outputArray.apply((servers) => {
     let output: pulumi.Output<string>[] = servers.map(s => pulumi.output(s))
    return output 
}
)

But not comfortable with it.

Wish it was clearer how Pulumi lifts all these promises. https://www.pulumi.com/docs/intro/concepts/programming-model/#outputs-and-strings aren’t super clear about the magic going on.

Also is there an approach to

get_or_create()

? Say a few stacks depend on a resource, but if it doesn’t exist it can get them. And other stacks can do the same, that way I don’t rely on running a specific stack first.

How do you manage DNS-related resources in Pulumi ? I have a Route53

Zone

which is global (ex: example.com) then I have

Record

for each environment (ex: dev.example.com, etc.) Should I create a

core

stack for the

Zone

and a

dev

stack for my dev

Record

? If so, how do I indicate in my

__main__.py

which resources should be deployed according to the stack that's currently selected ? Is there a native mechanism or should I just hack about ?

Hoping someone can help me. I'm running through this guide on Stack Reference, https://github.com/pulumi/examples/tree/master/aws-py-stackreference When I create department under the company directory, it won't allow me to create

pulumi stack init dev

as it says it already exists. What am I doing wrong?

How can I turn an existing Fargate cluster into something that can work with

@pulumi/awsx

? I can't find a "getCluster" method or anything.

getDefault

helpfully wants to create one for me, but we've already got existing infrastructure.

been reading the docs, but don't see examples of how one might go about writing test specs, did I miss it somewhere?

I've got an assertion failure that I don't understand:

panic: fatal: An assertion has failed: Expected diff to not require deletion or replacement during Update of urn:pulumi:deploy-test::deploy::aws:ecs/service:Service::xxx

I replaced dependencies for the Service, could that be the problem?

How can we restrict a Pulumi access-token to stacks of one Git repository? We’re going to use Pulumi in CI for our microservices. Each microservice’s deployment config is in its own Git repository. In the CI, we would like to use one service-account, here worked around with restricted access-tokens, for each microservice.

message has been deleted

Do you have any ETA for getting the 1.8.1 container image of pulumi?

Is there a way to provide a custom tag when using the

@pulumi/docker

buildAndPushImage()

(for example, a GIT_SHA), rather than the autogenerated tag that is created?

Is it possible to detect when Pulumi is running in watch mode to change resource behavior? For example, could a custom docker image resource be made that detects when Pulumi is running in watch mode and whenever there’s a change to source files, instead of rebuilding the image it syncs the files through a volume, allowing for stuff like hot-reloading? This would not be dissimilar from what Tilt and Skaffold allow you to do.

Where is the code for core of pulumi in (https://github.com/pulumi) ? - Is it using terraform ?

Is it necessary to have pulumi cli installed for my program that uses pulumi client library to run ?

is there a way to set common config to use for all stacks?

hi, I'm currently using Github provider to login to the pulumi console, how can I use the email provider to log in? I can't see an option to add an email based identity in the settings, just cloudflare, gitlab etc., tried the forget password option, but it says that I only have the Github provider for that email, so I'm unable to change password.

@white-balloon-205 Sorry I asked before, but not sure if you got it. Is there a way to create or refer to a resource? In this case it’s groups and users (aws IAM). I want to access a group and a user and create either if they don’t exist and add user to the said group if the association isn’t already set.

Is there a way to specify the target k8s cluster for

query-kubernetes

? like with a k8s.Provider eg

How should I got about making my own Pulumi provider from an existing Terraform provider ? I've taken a look at the pulumi bridge repository: https://github.com/pulumi/pulumi-tf-provider-boilerplate/ A lot of stuff seems hard-coded for internal pulumi purposes... I'd like to make a

pulumi-snowflake

provider, can someone give me some guidance here ? 🙂

Is there a way to pass two arguments using the

apply

method with Python?

template = lambda Topic, Endpoint: { "AWSTemplateFormatVersion": "2010-09-09",
    "Resources": {
        "MySubscription": {
            "Type": "AWS::SNS::Subscription",
            "Properties": {
                "Protocol": "email",
                "Endpoint": Endpoint,
                "TopicArn": Topic
            },
        }
    }
}

sns_email = cloudformation.Stack(
    "Cloudformation-email",
    template_body = (template(sns_topic.arn, Endpoint))
)