limited-rainbow-51650
01/20/2020, 11:10 AMcuddly-smartphone-89735
01/20/2020, 2:03 PMkubeconfig
parameter with the output of a Azure KubernetesCluster
resource. But for some reason, when I run pulumi up
before even provisioning anything, it fails because the k8s
resource already tries to connect to the cluster (which doesn't exist at this point in time). I thought that a missing dependency was the issue, but even when I specify the dependency explicitly, it will fail with the connection error. Any ideas? Basically I just want to provision a cluster (with azure provider) and then configure that same cluster (with k8s provider).nutritious-judge-27316
01/20/2020, 2:12 PMred-football-97286
01/20/2020, 2:47 PMlimited-rain-96205
01/20/2020, 7:18 PMfresh-summer-65887
01/20/2020, 8:57 PMpulumi up
takes 6 to 7 minutes. Is this typical? Seems a bit long....bored-river-53178
01/20/2020, 9:16 PMeager-gold-58845
01/21/2020, 1:22 AMruntime.registerStackTransformation(args => {
return {
...args,
props: {
...args.props,
tags: {
owner: "stewartnoll"
}
}
}
});
but ran into the problem pointed out in the question's thread where not all aws resources support a tag resulting in a failure at pulumi up
. Followed up by moving to a more explicit approach that sets tags on those things I specifically care about:
runtime.registerStackTransformation(args => {
if (args.type === 'aws:lambda/function:Function' || args.type === '<ANOTHER TYPE HERE>') {
return {
...args,
props: {
...args.props,
tags: {
owner: "stewartnoll"
}
}
}
}
return undefined;
});
Although this has the benefit of reducing cognitive load on future devs adding functions to the stack, there's still the issue of adding a different resource to the stack that supports tags but isn't captured in the condition. If this were dot net I'd use reflection to map args.type
to the dot net Type and check if the Type has the property Tags
which would cover all resource types (including those that haven't been created by aws yet). I've been Googling a bunch on how to do something similar in TypeScript but haven't had any luck. Does anyone know of a way to do this or a better approach?flat-insurance-25294
01/21/2020, 1:37 AMbetter-rainbow-14549
01/21/2020, 10:40 AMcold-motorcycle-78950
01/21/2020, 4:30 PMbig-potato-91793
01/21/2020, 4:31 PMError: ENOENT: no such file or directory, open '/Users/alexandrelemieux/tm/pulumi/ticketmaster/node_modules/grpc/node_modules/needle/test/keys/ssl.cert'
at Object.openSync (fs.js:448:3)
at Object.readFileSync (fs.js:348:35)
at Object.<anonymous> (/Users/alexandrelemieux/tm/pulumi/ticketmaster/node_modules/grpc/node_modules/needle/test/helpers.js:9:13)
at Module._compile (internal/modules/cjs/loader.js:738:30)
at Object.Module._extensions..js (internal/modules/cjs/loader.js:749:10)
at Module.load (internal/modules/cjs/loader.js:630:32)
at tryModuleLoad (internal/modules/cjs/loader.js:570:12)
at Function.Module._load (internal/modules/cjs/loader.js:562:3)
at Module.require (internal/modules/cjs/loader.js:667:17)
at require (internal/modules/cjs/helpers.js:20:18)
npm ERR! Test failed. See above for more details.
flat-insurance-25294
01/21/2020, 5:06 PMbroad-boots-45639
01/21/2020, 6:21 PM--set
. Pulumi looks to be writing these values into a yaml file in tmp, but they’re cleaned up as soon as the command fails:
Command failed: helm template /tmp/tmp-2518liO6nRLE4N1X/sumologic --name-template sumobundle --values /tmp/tmp-2518liO6nRLE4N1X/sumologic/values.yaml --values /tmp/tmp-25188Uk68Vj0j9UB.yaml --namespace sumologic
I’d like to validate the values in these files and confirm that the secrets are being passed in. Before I do something hacky, is there a better way I could go about troubleshooting this problem or maybe force Pulumi to retain its artifacts from the preview?incalculable-engineer-92975
01/21/2020, 8:21 PMfast-dinner-32080
01/21/2020, 8:39 PMcool-egg-852
01/21/2020, 9:41 PMelegant-dress-88912
01/22/2020, 5:30 AMpulumi up
shows secure outputs in plain text, is it a known issue? I am using pulumi random:
import * as random from "@pulumi/random";
...
const redisPassword = new random.RandomPassword("redis", {
length: 10,
special: false
});
export const redisStgPassword = redisPassword.result;
Per docs, pulumi should display at as`[secret]` : https://www.pulumi.com/docs/intro/concepts/programming-model/#stack-outputs and https://www.pulumi.com/docs/reference/pkg/nodejs/pulumi/random/#RandomPassword while in my case it displays it in plaintext every invocation of pulumi up
or pulumi stack output
I am using pulumi 1.8.1 and random 1.4.0limited-rainbow-51650
01/22/2020, 8:56 AMStructured Configuration
shows how to set a secret as part of structured config. But I’m missing what the type should be in my custom TS interface.
https://www.pulumi.com/docs/intro/concepts/config/#structured-configurationred-football-97286
01/22/2020, 11:51 AMfresh-summer-65887
01/22/2020, 3:07 PMbroad-dog-22463
01/22/2020, 3:16 PMbroad-dog-22463
01/22/2020, 3:17 PMbroad-dog-22463
01/22/2020, 3:17 PMfresh-summer-65887
01/22/2020, 3:38 PMpulumi up
wants to replace the cert. What I'm looking at now is adjusting the ordering in code so it matched what was previsioned previously.incalculable-engineer-92975
01/22/2020, 3:39 PMlate-army-57201
01/22/2020, 5:40 PMlate-army-57201
01/22/2020, 5:40 PMlate-army-57201
01/22/2020, 5:40 PMlate-army-57201
01/22/2020, 5:42 PM