OK, I'll start the TS questions. (Forgive my potentially incorrect terminology; gently correct me where needed.) I understand that properties of a class like

aws.ec2.Instance

are of type Input. How does one take the result of a function like

aws.getAmi

(which is a Promise, AIUI) and use it to specify a value for a property?

ready for some gross looking TS?

set the channel topic: All Typescript all the time! Noob friendly - no dumb questions.

set the channel topic: All Typescript all the time! Noob friendly - there are no dumb questions.

Ok so we are trying to decouple a hard dependency in how we run some tests so not depend on a

pulumi up

to generate our config. So far I’ve got a pre-commit hook:

Attempting to use ts-node to run arbitrary TS files

here’s what it’s running:

(forgive all the console logging)

We are leveraging the node config package to apply per environment ‘transforms’ on our default config. Works flawlessly for our pulumi deployments.

but what I want to do is pre-generate the resolved merge of the default and the environment configs and have them in the repo. Then when the test container runs, it’s got a per environment config json object ready to use and we select it via a simple env variable passed to the container

the code above mostly works and generates the json files. However it’s creating unique files but they all have the same contents namely, the config of our ‘alpha’ environment (the first one).

output of console logging:

so I’m sure it’s something to do with a single process or invocation or something

@orange-tailor-85423 Before we get to your actual issue just 2 quick remarks: 1. Please do yourself and your colleagues a favor and don’t name variables

c

or any other single character 😄. It just makes reading the code harder even if it’s somewhat clear from the surrounding context what the c stands for (but consumes more brain CPU :-P). In your example I would call this variable

configFileName

instead. 2. You can turn

import fs = require('fs');

into

import * as fs from 'fs'

. Just looks more ES6 native 😉 Coming to your actual problem: In line 15 you’re loading the merged config by calling require(‘config’). This will load the merged config based on your environment variables during the first .forEach loop iteration. However in the second loop iteration - despite you having changed the environment variables - the

require('config')

call will return exactly the same thing as in the first one. In general in node.js multiple calls of require(‘asdf’) will always return the exact same thing (this also applies to ES6 imports

import ... from 'asdf'

for that matter). This is described in further detail here: https://nodejs.org/api/modules.html#modules_caching . I haven’t tried it out myself but it looks like you should be able to use https://github.com/lorenwest/node-config/wiki/Using-Config-Utilities#loadfileconfigsdirectory (e.g.

require('config').util.loadFileConfigs(path.join(__dirname, 'config'))

instead of the plain

require('config')

to load the merged config without experiencing the caching problem.

Hello!

I am trying to deploy google cloud functions in typescript

But pulumi does not seem to have access to the private npm package of my organization. Can someone please help?

What error do you see?

Cannot access npm package

which is a private package created for my organization @org/private_package

I mean, what command are you running and what output are you seeing? As far as I’m aware, Pulumi does nothing to specifically prevent using a private NPM package, but you will have to be authenticated as normal. In fact, I don’t believe Pulumi even invokes NPM on your behalf, so I’d be surprised if a Pulumi cli invocation led to this error.

I run

pulumi up

locally

and I get a

npm 404 error: cannot find @org/private...

I can add packages via yarn or npm locally

let me delete my local

npm_modules

folder and try to install locally again