i'm not sure which one is gonna be run first, so i would need to check if the kinesis stream already exists in order to avoid creating it

so imagine i run pulumiA first, and it created the kinesis stream

then i run pulumiB, which checks for existence of said kinesis strem. it exists, so it does not create it

then, i update something on pulumiA and run it again

as stream already exists, i do not do a new aws.kinesis.Stream

and the result is that pulumi thinks i want to delete that stream

not sure if it makes sense what i'm trying to do

😄

hey folks, there seems to be bigger bug being introduced with

"@pulumi/kubernetes": "0.18.0",

or

"@pulumi/pulumi": "0.16.7",

https://github.com/pulumi/pulumi/issues/2170#issuecomment-447143452

Is this the channel to ask/discuss implementation details? Or is there another one, more dedicated for such conversations?

Problem I have a bunch of static html websites that need hosting. Other infrastructure is already in AWS (S3 buckets or EC2). However, because the web-pages need to respond to the client’s

Accept-Language

header or a saved cookie, I think we’ll have to do some URL rewriting (to ensure transparency and SEO). For example,

foo.bla/site.html

should forward to

foo.bla/en/site.html

by default, or whatever language the header/cookie contained. Solutions 1. Client-side Javascript “cloaking” etc are off the table, I think. Doesn’t play well with SEO and is annoying for clients. 2. Use AWS S3 and web-page redirect: https://docs.aws.amazon.com/AmazonS3/latest/dev/how-to-page-redirect.html 3. Host the site in a Kubernetes container with nginx/apache. Of 2. and 3. I am leaning towards 2. because it’s probably easiest to set up for now. Both could be implemented using Pūlumi, and that would be the right way to go about it. What are your thoughts, and does Pūlumi handle the redirect configurations for 2.?

hi guys, where can i find the documentation for pulumi python

Hello, I was wondering what would be the best way to handle some applications specific users/credentials with pulumi ? ie. postgres Before diving too deep in researches I could use some thoughts from you guys 🙂

is there any way to get an azure subscription ID from one of the resources? they should know it right?

+ ├─ kubernetes:apiextensions.kubernetes.io:CustomResourceDefinition azureassignedidentities.aadpodidentity.kubernetes.io creating failed error: Plan apply failed: the server could not find the requested resource

I've created a new stack as a user in my org, but it's showing up under my user account, not my team/org account. Is there a CLI action to transfer it or rename the stack so that it is accessible from org-stacks?

nevermind, I just exported+imported and prefixed with my org's name

that seems to have worked

I’ve been playing with wiring up Pulumi as a CD step in Azure DevOps. They use the web based Visual Studio Code editor for the output of each step. VSC highlights urls and lets you ctrl+click them to launch a browser. Super convenient. It’d be cool to be able to use/do that from that from https://app.pulumi.com. Don't know if it's on the road map

Ran my first

pulumi up

and this is magical.

can anyone point me to a code example of creating a custom pulumi resource - ie, wrapping up a call to a 3rd party api, or wrapping a command line tool?

@white-balloon-205 It seems like the

gcp

Cluster

resource is unable to scale up an already existing cluster by changing its

nodeCount

or maybe I’m missing something ?

Type                                 Name                                       Status                   Info
     pulumi:pulumi:Stack                  REDACTED
     └─ REDACTED:Cluster  REDACTED-cluster
 +-     └─ gcp:container:Cluster          REDACTED                   **replacing failed**    [diff: ~initialNodeCount]; 1 error

Diagnostics:
  gcp:container:Cluster (REDACTED):
    error: Plan apply failed: googleapi: Error 409: Already exists: projects/REDACTED/zones/REDACTED/clusters/REDACTED-cluster., alreadyExists

USPs of Pulumi

- How different is Pulumi from JenkinsX?

hello world

Just discovered Pulumi. Holy wow. LOVE the value offer here. Going to be playing with this tonight. I’ve got a use case where we’re going to start spinning up an env. per pull request in Github. So going to try out that use case using Pulumi. 🚀

Does anyone have experience with the Pulumi Github App? I've added it to a repository, but aren't seeing anything show up on Pull Requests. Is there any specific config needed to activate it?

Hello there!

Hi! I have an issue with Kubernetes provider. According to documentation (https://pulumi.io/quickstart/kubernetes/setup.html) it’s possible to use a provider that doesn’t use local

~/.kube

config but rather configuration exported for example from GKE cluster:

@white-balloon-205 I have a weird behaviour. I’m provisioning a gke cluster with pulumi, no issue here. But if I try to delete it (removing it from the stack), the update went well, everything is flagged as deleted and exit without error, yet the cluster is still there in gke. Is this a problem with the terraform provider under the hood, or is it a feature or intended (and if so should be explicitly mentioned) ?

Hey everyone! I've been working on a Pulumi program that targets a Kubernetes cluster and am a little confused as to how providers work when targeting a Helm chart. On all the other K8s objects (Deployment, Service, etc) I can explicitly set the provider on the CustomResourceOptions but the Helm Chart exposes ComponentResourceOptions which takes a Record of keyed providers. It's not really clear from the docs how these keys are supposed to be used. I just want to ensure that the Helm resource is correctly targeting the Kubernetes instance from my provider but right now I'm seeing it attempt to target whatever context is currently set in my local kubeconfig

Hello again! Today when I was trying to setup multi-stack configuration with exporting kubeconfig to another stack I found a strange issue with assembling kubeconfig yaml used as an export. This example shows how to create that kubeconfig: https://github.com/pulumi/examples/blob/master/gcp-ts-gke/cluster.ts#L27-L56. What I tried is to replace this part of the code:

export const k8sConfig = pulumi.
    all([ k8sCluster.name, k8sCluster.endpoint, k8sCluster.masterAuth ]).
    apply(([ name, endpoint, auth ]) => {
        const context = `${gcp.config.project}_${gcp.config.zone}_${name}`;
        return `apiVersion: v1...

with:

export const k8sConfig = pulumi.
    all([ k8sCluster.project, k8sCluster.region, k8sCluster.zone, k8sCluster.name, k8sCluster.endpoint, k8sCluster.masterAuth ]).
    apply(([ project, region, zone, name, endpoint, auth ]) => {
        const location = region || zone
        const context = `${project}_${location}_${name}`
        return `apiVersion: v1...