pulumi-community #general

early-intern-90238

10/07/2019, 11:22 PM

Hey guys, do you think you will be adding ReleaseChannel to kubernetes soon?

early-match-56268

10/07/2019, 11:30 PM

hey all, I just upgraded to 1.2 and now pulumi is trying to add annotations such as the following to the resources in my k8s cluster

Copy code

~ metadata: {
          + annotations: {
              + <http://pulumi.com/initialApiVersion|pulumi.com/initialApiVersion>: "v1"
            }
        }

this is causing resources to try to update/delete when they have not changed. Is there any way to work around this?

salmon-account-74572

10/08/2019, 3:44 AM

Does anyone have any "best practices" or recommended guidelines with regard to Pulumi and version control? What files, if any, should be excluded?

elegant-dress-88912

10/08/2019, 1:16 PM

how can I specify default values for stack configuration? For now the only way I see is:

Copy code

const config = new pulumi.Config();
const configVar:string = config.get('configVar') ? config.get('configVar') : 'someDefaultValue'

broad-dog-22463

10/08/2019, 1:17 PM

You can do something like

broad-dog-22463

10/08/2019, 1:18 PM

const config = new Config(); const myValue = config.get(“variable”) || “default”;

stocky-island-3676

10/08/2019, 1:25 PM

Someone knows about this?

early-intern-90238

10/08/2019, 2:00 PM

Hey guys, quick question on how you are doing branching with dev, stage, and prod. I get you can setup branch mapping using ci.json, that's fine and makes sense. But first question, how are you promoting your builds into production? Are you using Releases to trigger that? That was what I was going to do...Secondly, how are you handling developer stacks? Do you host those in cloud or on dev machines? How are you handling those stacks in Pulumi? A stack per a dev?

nice-cat-91582

10/08/2019, 2:57 PM

Does anyone ever have issues with

pulumi up

not picking up changes to Lambda environment variables?

nice-cat-91582

10/08/2019, 2:57 PM

It seems like sometimes I have to change the variable name for it to pick up, or in rare situations no matter what I do I just have to go edit them manually in AWS'

quaint-teacher-33292

10/08/2019, 4:54 PM

I updated my setup from 0.17.21 to 1.2.0 (and appropriate plugins). Now I'm trying to raise

minMasterVersion

of my GCP k8s cluster, which properly shows it needs updating (as opposed to recreating). However, I then have a custom pulumi k8s provider stitched together based on

pulumi.all([ cluster.name, cluster.endpoint, cluster.masterAuth ])

And all k8s resources are using this explicit

k8s.Provider

, and they're all showing

replace

strategy if I decide to raise my minMasterVersion. I don't remember this happening with 0.17.21, which has me very worried. I wanted to use the selective update with

--target urn

, but this has not landed in 1.2.0, despite the changelog indicating such. Did anyone face this? Can I expect all my stuff using this

k8s.Provider

to remain the same as long as that provider is created/configured the same at runtime?

plain-businessperson-30883

10/08/2019, 5:22 PM

Does anyone know how to retrieve the token from a freshly created ServiceAccount in Pulumi? Since the secret name of the token is dynamic, I'm not very sure on how to retrieve it in Pulumi.

nice-cat-91582

10/08/2019, 9:05 PM

👋 trying to get Sequelize to work in a CallbackFunction, but I'm getting

the function form was not understood.

when

Sequelize.UUID

is parsed

nice-cat-91582

10/08/2019, 9:05 PM

found this in the Pulumi source:

nice-cat-91582

10/08/2019, 9:05 PM

Copy code

if (funcString.startsWith("[Function:")) {
        return [`the function form was not understood.`, <any>undefined];
    }

nice-cat-91582

10/08/2019, 9:05 PM

Does that just mean... there's no way to do this?

purple-appointment-43233

10/08/2019, 10:55 PM

Hey all, I’m returning to a stack that I haven’t used in a few weeks and Pulumi seems to be hanging indefinitely on a call to

aws.route53.getZone({ name: domainParts.parentDomain }).then(zone => zone.id)

. This is a copy & paste (and very lightly edited) version of the published example on deploying a static website to S3. Any thoughts as to what could be going on? The only thing I can think of that materially changed was that I upgraded to catalina, and had to upgrade some node packages to get it to build…

white-balloon-205

10/08/2019, 11:36 PM

Just a heads-up - we've heard a couple reports in the last 24 hours of folks upgrading to macOS Catalina and using Node 12 hitting hangs when using Pulumi - see https://github.com/pulumi/pulumi/issues/3309 for details. We are actively looking into this, but for now, we suggest that folks upgrading to Catalina ensure they are using Node 10 (the current LTS release).

early-intern-90238

10/08/2019, 11:58 PM

From what I hear, you should probably avoid upgrading to Catalina in general haha.... 🙂

damp-notebook-63293

10/09/2019, 7:36 AM

Is it just me or Pulumi has trouble interpolating values using Downward API? I have the following set in my Deployment, but

DISCOVERY_HOSTNAME

resolves to a blank value.

Copy code

env: [
  {
    name: 'DISCOVERY_HOSTNAME',
    valueFrom: {
      fieldRef: {
        fieldPath: 'status.podIP'
      }
    }
  },
],

red-football-97286

10/09/2019, 10:02 AM

After a bit of help trying to get pulumi aws with Python to work.

Copy code

pulumi:pulumi:Stack (dev-dev):
    Traceback (most recent call last):
      File "C:\pulumi\bin\pulumi-language-python-exec", line 14, in <module>
        import pulumi
    ModuleNotFoundError: No module named 'pulumi'
    It looks like the Pulumi SDK has not been installed. Have you run pip install?
    If you are running in a virtualenv, you must run pip install -r requirements.txt from inside the virtualenv.

    error: an unhandled error occurred: Program exited with non-zero exit code: 1

red-football-97286

10/09/2019, 10:02 AM

Done some googling and looked like a bug a year ago.

red-football-97286

10/09/2019, 10:02 AM

I've done all the steps to install.

red-football-97286

10/09/2019, 10:03 AM

I'm on Windows

red-football-97286

10/09/2019, 10:29 AM

Sorted it now. I was using the wrong virtual environment for python.

nice-cat-91582

10/09/2019, 10:35 AM

https://pulumi-community.slack.com/archives/C84L4E3N1/p1570579979425900?thread_ts=1570568724.411700&cid=C84L4E3N1 Anyone have advice on how they're structuring lambda projects that use AssetArchives instead of magic functions? It seems like the only reasonable way to do it is having multiple

package.json

files - one for each function. I'm imagining this will get really messy on deploy, as I would need to

npm install

in every folder on every deploy

better-rainbow-14549

10/09/2019, 11:35 AM

I've just updated kubernetes from 1.1.0 to 1.2.1 and it wants to redeploy every configmap (from using binaryData property to data) and thus redeploy everything that uses those config maps. is that expected? will it actually redeploy things?

incalculable-engineer-92975

10/09/2019, 1:42 PM

Suggestion: add a 'clear' or 'reset' command for 'pulumi stack'. This would be equivalent to exporting the stack, removing all the resources and re-importing the stack. This should do a 'are you sure?' prompt. I need this on a semi-regular basis when someone destroys a sandbox cluster but forgets to do an istio destroy (or something else running on the cluster).

brief-yacht-31759

10/09/2019, 3:23 PM

Hey, keen to POC Pulumi. Have some best practice questions if that is ok. In general, how are people mapping git repos/branches to pulumi stacks to logical infrastructure environments (environments)? I suppose an initial approach could be to have a git repo, with a branch per environment, then have a pulumi stack per environment. Where I am working now, an environment is basically AWS components, helm/kubernetes components, and then ansible/bash for some glue, so I am keen to automate straight away and think about the CI pipeline for progressing changes through multiple environments straight away.

rhythmic-finland-36256

10/09/2019, 5:55 PM

Using

ComponentResource

with shared

ComponentResourceOptions

passed down to the child resources seems to mutate the options - which leads to confusing error messages of duplicate resource aliases. Do I need to construct a new options object for each child resource?