loud-scientist-13640
11/30/2018, 4:36 PMcold-coat-35200
11/30/2018, 5:19 PM├── bastion // pulumi project
├── dliver //pulumi project
├── modules // shared custom modules
├── node_modules // shared node_modules
└── static
bastion/dliver has it's own package.json and pulumi related files, but their node_modules directory is empty, they only using the shared node_modules.
It work fine, until I'm trying to use a custom dynamic provider, in that case I got this error during the preview:
Diagnostics:
pulumi:providers:pulumi-nodejs (default):
error: could not read plugin [/home/ncsibra/.pulumi/bin/pulumi-resource-pulumi-nodejs] stdout: EOF
pulumi:pulumi:Stack (bastion-bastion-dev):
(node:2514) ExperimentalWarning: queueMicrotask() is experimental.
internal/modules/cjs/loader.js:589
throw err;
^
Error: Cannot find module '/home/ncsibra/dev/prmrgt-infra/pulumi/bastion/node_modules/@pulumi/pulumi/cmd/dynamic-provider'
at Function.Module._resolveFilename (internal/modules/cjs/loader.js:587:15)
at Function.Module._load (internal/modules/cjs/loader.js:513:25)
at Function.Module.runMain (internal/modules/cjs/loader.js:760:12)
at startup (internal/bootstrap/node.js:303:19)
at bootstrapNodeJSCore (internal/bootstrap/node.js:872:3)
The module is in the /home/ncsibra/dev/prmrgt-infra/pulumi/node_modules/@pulumi/pulumi/cmd/dynamic-provider
directory, not in the /home/ncsibra/dev/prmrgt-infra/pulumi/bastion/node_modules/@pulumi/pulumi/cmd/dynamic-provider
.
Without the dynamic provider, the preview runs fine.
I think the problem is not the dynamic provider, because with the old structure(it was one pulumi project, which contained the modules and the node_modules directory too with 1 package.json) everything worked fine.
Any idea why it's not find the @pulumi/pulumi/cmd/dynamic-provider
module, but find everything else in @pulumi/pulumi
and @pulumi/aws
?bitter-oil-46081
11/30/2018, 6:18 PMbulky-policeman-29913
11/30/2018, 6:46 PMbulky-policeman-29913
11/30/2018, 6:49 PMorange-tailor-85423
11/30/2018, 7:25 PMtall-monitor-77779
11/30/2018, 7:26 PMCannot find module 'spdx-license-ids' from 'scan.js'
when running tests via jest https://pulumi-community.slack.com/archives/C84L4E3N1/p1543587290005700most-pager-38056
11/30/2018, 8:52 PM### STARTED Pulumi Deploy (Current Stack) 20:40:29Z
(pulling, digest, status, etc…)
### FAILED Pulumi Deploy (Current Stack) 20:40:30Z (97ms)I can run
pulumi update/preview
locally and i’ve setup my .pulumi/ci.json
and the workflow secrets correctly, so i’m not sure how to debug this. ☹️billowy-television-23506
12/01/2018, 10:12 PMfaint-motherboard-95438
12/03/2018, 3:30 PMgcp.container.Cluster
to create and manage a cluster with pulumi. I’m still in the learning phase, so I’m doing a lot of trials and errors so I have to update and rebuild the stack often. I changed the way the cluster is named and as expected, pulumi decided to update it (actually, replaced it). But instead of having my new cluster up and running I have now 2 clusters, the new and the old one. I suppose the old one should have been deleted in a replace operation, but it’s actually not (and no error reported about any issue that would have prevented it). I’m well aware that’s not really a daily use case, but anyway, it feels like a bug.bulky-policeman-29913
12/03/2018, 7:57 PMbulky-policeman-29913
12/03/2018, 7:58 PM/home/user/dev/pulumi/bean/node_modules/@pulumi/pulumi/config.js:141
source-map-support.js:419
throw new ConfigMissingError(this.fullKey(key));
^
Error: Missing required configuration variable 'aws:region'
source-map-support.js:422
please set a value using the command `pulumi config set aws:region <value>`
at Config.require (/home/svause/dev/pulumi/bean/node_modules/@pulumi/pulumi/config.js:141:19)
at exports.region.utilities.requireWithDefault (/home/svause/dev/pulumi/bean/node_modules/@pulumi/config/vars.ts:44:78)
at Object.requireWithDefault (/home/svause/dev/pulumi/bean/node_modules/@pulumi/utilities.ts:45:16)
at Object.<anonymous> (/home/svause/dev/pulumi/bean/node_modules/@pulumi/config/vars.ts:44:44)
at Module._compile (internal/modules/cjs/loader.js:688:30)
at Object.Module._extensions..js (internal/modules/cjs/loader.js:699:10)
at Module.load (internal/modules/cjs/loader.js:598:32)
at tryModuleLoad (internal/modules/cjs/loader.js:537:12)
at Function.Module._load (internal/modules/cjs/loader.js:529:3)
bulky-policeman-29913
12/03/2018, 7:58 PMelegant-crayon-4967
12/03/2018, 9:48 PMadventurous-stone-37349
12/03/2018, 10:03 PMadamant-restaurant-73893
12/03/2018, 10:19 PMmost-pager-38056
12/03/2018, 10:45 PMfaint-motherboard-95438
12/03/2018, 11:09 PMcluster-admin
for this cluster beforehand (as stated here : https://cloud.google.com/kubernetes-engine/docs/how-to/role-based-access-control#setting_up_role-based_access_control), see where I’m going with that ?
I need the cluster to be created to be able to make this binding before being able to create any other Role or ClusterRole, but since the cluster creation and the roles are part of the automation, the only way everything works as expected (in one shot) would be to create this RoleBinding right after the cluster is ready inside the pulumi stack deployment. Doing so would require to get my current active google identity to make the right binding on the right account.
How/Can I do that within pulumi with the @pulumi/kubernetes
package (I’m using the typescript flavor) ?billowy-television-23506
12/03/2018, 11:45 PMMicrosoft.Web/sites
in the siteConfig
section there is:
"alwaysOn": true,
"linuxFxVersion": "DOCKER CONTAINER"
The Pulumi SDK supports alwaysOn
is there a way to pass “linuxFxVersion”?damp-pillow-67781
12/04/2018, 1:08 AMPlan apply failed: unable to fetch resource description for extensions/v1beta1: Unauthorized
prehistoric-analyst-52684
12/04/2018, 11:15 AMfaint-motherboard-95438
12/04/2018, 11:20 AMerror: Error: Invoke of 'gcp:serviceAccount/getAccount:getAccount' failed: undefined (undefined)
at Object.<anonymous> ([...]/node_modules/@pulumi/pulumi/runtime/invoke.js:82:23)
at Generator.next (<anonymous>)
at fulfilled ([...]/node_modules/@pulumi/pulumi/runtime/invoke.js:17:58)
coming from :
const account = gcp.serviceAccount.getAccount({ accountId: '[account_id]' })
I followed the function declaration from getAccount.d.ts
, I’m missing something hereloud-scientist-13640
12/04/2018, 3:26 PMfull-dress-10026
12/04/2018, 10:51 PMlet alertsTopicSubscription = new aws.sns.TopicSubscription("alerts-lambda-subscription", {
topic: alertsSnsTopic,
protocol: "lambda",
endpoint: "my-lambda-arn"
});
However, if I go to the AWS console, the Lambda function does not have the SNS topic listed as a trigger. Is there another step I need to perform to get this to work as expected?full-dress-10026
12/05/2018, 12:31 AMaws.lambda.Permission
first. Is there a nice API to do both of these things?faint-motherboard-95438
12/05/2018, 6:51 PMcredentials
property of the gcp
package Provider
I pass down my components.adamant-restaurant-73893
12/05/2018, 7:04 PMcuddly-barista-79466
12/05/2018, 8:18 PMcuddly-barista-79466
12/06/2018, 2:23 PMfull-dress-10026
12/06/2018, 9:34 PMFunction.get
was deleted externally. I have commented out the Function.get
code but now Pulumi is stuck when running pulumi refresh
with:
Preview failed: refreshing urn:pulumi:app-prod::app::aws:lambda/function:Function::send-alert-lambda: InvalidParameter: 1 validation error(s) found.
- minimum field size of 1, GetFunctionInput.FunctionName.
full-dress-10026
12/06/2018, 9:34 PMFunction.get
was deleted externally. I have commented out the Function.get
code but now Pulumi is stuck when running pulumi refresh
with:
Preview failed: refreshing urn:pulumi:app-prod::app::aws:lambda/function:Function::send-alert-lambda: InvalidParameter: 1 validation error(s) found.
- minimum field size of 1, GetFunctionInput.FunctionName.
white-balloon-205
12/06/2018, 11:54 PM