pulumi-community #general

Channels

general

swift-painter-31084

07/10/2019, 4:31 PM

My Callback Functions' package size is getting quite large as I have several in a project that contains many dependencies. The explicitly defined functions are much smaller and independent, but I really like the convenience of callback/magic functions. Is there a recommended practice for limiting/isolating dependencies included in inline functions?

swift-painter-31084

07/10/2019, 4:31 PM

millions-judge-24978

07/10/2019, 6:05 PM

I've just published https://github.com/timmyers/pulumi-k8s-metrics-server, a pulumi native module for deploying

metrics-server

kubernetes

, and an alternative to using the helm chart. It is in an early stage, but I believe it can be useful already. Feedback and PR's welcome!

🎉 1

🚀 2

bitter-island-28909

07/10/2019, 6:59 PM

Is the Pulumi backend having issues? My stack was working this morning, but all my attempts to

pulumi up

this afternoon hang forever in this state:

plain-businessperson-30883

07/10/2019, 7:53 PM

Hello. Is there any limitation when exporting a provider? If I try to use a k8s provider from a stack reference I get this error:

error: Running program '/Volumes/Projects/Credijusto/infra/applications/prometheus-operator' failed with an unhandled exception:
    TypeError: provider.getPackage is not a function
        at convertToProvidersMap (/Volumes/Projects/Credijusto/infra/node_modules/@pulumi/pulumi/resource.js:198:25)
        at new Resource (/Volumes/Projects/Credijusto/infra/node_modules/@pulumi/pulumi/resource.js:147:19)
        at new ComponentResource (/Volumes/Projects/Credijusto/infra/node_modules/@pulumi/pulumi/resource.js:335:9)
        at new CollectionComponentResource (/Volumes/Projects/Credijusto/infra/node_modules/@pulumi/kubernetes/yaml/yaml.js:60:9)
        at new Chart (/Volumes/Projects/Credijusto/infra/node_modules/@pulumi/kubernetes/helm/v2/helm.js:62:9)
        at Object.<anonymous> (/Volumes/Projects/Credijusto/infra/applications/prometheus-operator/index.ts:8:1)
        at Module._compile (internal/modules/cjs/loader.js:776:30)
        at Module.m._compile (/Volumes/Projects/Credijusto/infra/node_modules/ts-node/src/index.ts:439:23)
        at Module._extensions..js (internal/modules/cjs/loader.js:787:10)
        at Object.require.extensions.<computed> [as .ts] (/Volumes/Projects/Credijusto/infra/node_modules/ts-node/src/index.ts:442:12)

    (node:99408) [DEP0018] DeprecationWarning: Unhandled promise rejections are deprecated. In the future, promise rejections that are not handled will terminate the Node.js process with a non-zero exit code.

I can get around this one defining the

providers

in the ComponentResourceOptions param (

providers: { kubernetes: myProvider }

), but then the following happens:

error: Running program '/Volumes/Projects/Credijusto/infra/applications/prometheus-operator' failed with an unhandled exception:
    TypeError: provider.urn.promise is not a function
        at /Volumes/Projects/Credijusto/infra/node_modules/@pulumi/pulumi/runtime/resource.js:226:52
        at Generator.next (<anonymous>)
        at fulfilled (/Volumes/Projects/Credijusto/infra/node_modules/@pulumi/pulumi/runtime/resource.js:17:58)
    error: Running program '/Volumes/Projects/Credijusto/infra/applications/prometheus-operator' failed with an unhandled exception:
    TypeError: provider.urn.promise is not a function
        at /Volumes/Projects/Credijusto/infra/node_modules/@pulumi/pulumi/runtime/resource.js:226:52
        at Generator.next (<anonymous>)
        at fulfilled (/Volumes/Projects/Credijusto/infra/node_modules/@pulumi/pulumi/runtime/resource.js:17:58)
    error: Running program '/Volumes/Projects/Credijusto/infra/applications/prometheus-operator' failed with an unhandled exception:
    TypeError: provider.urn.promise is not a function
        at /Volumes/Projects/Credijusto
.
.
.
// It happens recursively.

Any clues on this?

important-leather-28796

07/10/2019, 8:53 PM

In our ci that runs on our

develop

branch, we execute

pulumi preview

as a sanity check before it is merged to

master

. Generally speaking, our gcloud credentials are provided via env

GOOGLE_CLOUD_KEYFILE_JSON

. Is there a recent pulumi update that could be causing:

error: Get <https://35.226.191.153/openapi/v2?timeout=32s>: error executing access token command "gcloud config config-helper --format=json": err=exit status 1 output= stderr=ERROR: (gcloud.config.config-helper) You do not currently have an active account selected.
Please run:

  $ gcloud auth login

I haven’t any idea why a gcloud config would be called here in our ci.

modern-bear-85657

07/10/2019, 9:39 PM

I’m getting this error when testing usage of the

aws.ssm.getParameter()

function:

TypeError: Cannot read property 'invoke' of undefined
      at debuggable_1.debuggablePromise.Promise (/path/to/my/project/node_modules/@pulumi/pulumi/runtime/invoke.js:63:114)

cool-egg-852

07/11/2019, 4:34 AM

Is there any way to stop pulumi from detecting that the resources have changed? In https://github.com/banzaicloud/banzai-charts/tree/master/vault-secrets-webhook, every time I run pulumi up it wants to make changes because it’s generating the cert and such new.

colossal-room-15708

07/11/2019, 4:45 AM

Has anybody here gone from Troposphere to Pulumi? Looking for experiences and reasons why you moved to Pulumi. I have a customer that is currently using Troposphere (which I don't know at all) and I'm thinking of using Pulumi for them. Looking for reasons why that would be a good idea.

fast-motherboard-21624

07/11/2019, 6:09 AM

hey peeps! trying to add an AWS Fargate Task execution to a

cloud.API

route. getting a weird promise exception thrown and can't really understand where the exception is happening

fast-motherboard-21624

07/11/2019, 6:09 AM

task:

new aws.Task('curlbin', {
      image: 'byrnedo/alpine-curl',
      command: [
        '-H',
        'X-Status: Awesome',
        '<https://postb.in/1562821941108-3337054019793>',
      ],
    })
      .run({
        environment: {},
        host: { os: 'linux' },
      })
      .catch(e => {
        console.log('failed to run task', e);
      })
      .finally(() => {
        console.log('finished tas');
      });
  } catch (e) {
    console.log('failed to run task', e);
  }

error:

2019-07-11T06:03:59.645Z 474f76ff-9f41-4154-8f53-9cf9cc000e9a (node:1) UnhandledPromiseRejectionWarning: Error: Cannot find module '@pulumi/cloud/index.js'
at Function.Module._resolveFilename (module.js:547:15)
at Function.Module._load (module.js:474:25)
at Module.require (module.js:596:17)
at require (internal/module.js:11:18)
at /var/task/__index.js:179:34
at __f2 (/var/task/__index.js:213:6)
at next (/var/task/__index.js:239:17)
at /var/task/__index.js:169:9
at Generator.next (<anonymous>)
at /var/task/__index.js:121:71

fast-motherboard-21624

07/11/2019, 6:10 AM

woudl post a github issue but not exactly sure which repo to post in

fast-motherboard-21624

07/11/2019, 6:10 AM

when i comment out the task

run

, no error occurs

fast-motherboard-21624

07/11/2019, 6:32 AM

hmmm seems that scope was the issue

fast-motherboard-21624

07/11/2019, 6:32 AM

i had defined the

Task

INSIDE my

API

handler route

fast-motherboard-21624

07/11/2019, 6:32 AM

when i moved it out of that scope, it worked 🙂

fast-motherboard-21624

07/11/2019, 6:33 AM

and the dependency tree when i `pulumi up`'ed looks more right

bored-river-53178

07/11/2019, 9:25 AM

how can I get the value of "aws:region" from pulumi config?

jolly-egg-4894

07/11/2019, 9:43 AM

const awsConfig = new pulumi.Config("aws");
const awsRegion = awsConfig.get("region");

brief-school-94535

07/11/2019, 11:03 AM

Hi guys I'm getting an error when trying to deploy to GKE using pulumi. My code was working for awhile & hasn't changed but today I ran it and it fails with this error. Is anyone else having this issue?

-.sh

colossal-room-15708

07/11/2019, 11:08 AM

Customer asked me this today: Could I run pulumi completely cut off from the pulumi service by using state on S3 and using pulumi login against that state? I wasn't 100% sure about this, I saw some GitHub issues and PRs that worked on S3 state (although I can't find any documentation on how to configure and log in to S3 state), but I also wasn't sure about the "not using the pulumi service" aspect of this question.

acoustic-leather-88378

07/11/2019, 12:00 PM

Hi all, this might be a potentially silly question but thought I'd get some feedback anyway. Given the example of a Kubernetes

ReplicaSet

as part of a Pulumi managed deployment, what are the current patterns people are using to handle the updating of the `replica`'s value and the fact that it has now diverged from the initial state. I.e. Post stack deployment, a developer scales (legitimately) the replicas, meaning the stack state and the deployment state has diverged. If I ran

pulumi up

again, that

replica

value would be reverted back to it's initial value I assume. If the number of replicas being updated externally is a valid use case, how are teams handling the fact that certain properties should not be reverted to the stack state once the stack is run again? I guess this leads to a more general question around how (if it all) to handle valid/allowed changes to the managed resource directly and how/if the stack is then "back updated". Is the advice to simply not do/allow that but instead ignore any ephemeral changes and encourage always updating the stack instead? Any feedback appreciated...

gray-lawyer-89054

07/11/2019, 12:57 PM

Hi all, what is the best practice to handle secrets generated in pulumi for ephemeral env? For ex. I want to create new instance of mssql server on Azure with admin password in pulumi. One way which comes to my mind is to handle it with Azure Key Vault to not loose this password but maybe there is better approach which works natively with pulumi. Thanks

brief-school-94535

07/11/2019, 1:55 PM

https://pulumi-community.slack.com/archives/CDE799L1M/p1562844242061100

rapid-eye-32575

07/11/2019, 2:00 PM

Hey, I've got a stack in peril, because I did something stupid: I wanted to migrate a stack from a personal account to an organization and did so by just exporting the stack, selecting the organization stack and importing it. Afterwards I deleted the old stack. The problem is - which is kind of obvious now that it's broken - that I can't use it anymore since it used the service secret provider and that provider's is still pointing to the deleted stack. Therefore I get errors along the line of

error: could not deserialize deployment: decrypting secret value: [404] Not Found: Stack '...' not found

. Simply changing the owner in the state isn't working and only prints

error: could not deserialize deployment: decrypting secret value: [400] Message authentication failed

when trying to import it. I tried changing the secrets provider to type

passphrase

and set a salt and regenerating all secrets with the corresponding passphrase which then lead to

error: could not deserialize deployment: invalid character 'O' looking for beginning of value

when trying to import the stack. Is there any chance to get this working again?

brave-angle-33257

07/11/2019, 2:53 PM

does anyone know why the stack traces on node don’t seem to line up at all with the actual line numbers?

brave-angle-33257

07/11/2019, 2:53 PM

error: Running program '/data/pulumi/infra/azure/compute-api-docker' failed with an unhandled exception:
    SyntaxError: Unexpected token u in JSON at position 0
        at JSON.parse (<anonymous>)
        at ComputeDeployment.go (/data/pulumi/shared-ts/azure/compute-deployment.ts:279:31)
        at new ComputeDeployment (/data/pulumi/shared-ts/azure/compute-deployment.ts:54:14)
        ...

sparse-planet-30952

07/11/2019, 3:03 PM

Hello Pulumi community! I have just recently stumbled on Pulumi and I am enjoying it a ton, even thinking about migrating my company's terraform repo to Pulumi! However, I would like to know if any frameworks, best practices, design patterns for Pulumi exist and if any trends on using JS with IaC are emerging? Cheers 🍻

better-rainbow-14549

07/11/2019, 3:11 PM

I've got a strange thing where pulumi constantly wants to replace some kubernetes deployments, and the only thing in the diff is

+ volumeMounts: []
+ volumes                      : []

better-rainbow-14549

07/11/2019, 3:12 PM

anybody had that? the change always fails with "Failed to move on replicaset" or something