red-energy-90711
10/02/2020, 9:55 PMlimited-rainbow-51650
10/05/2020, 8:36 AMstack.SetConfig(ctx, "osimis.orthanc:config.name", auto.ConfigValue{Value: customer})
stack.SetConfig(ctx, "osimis.orthanc:config.domain", auto.ConfigValue{Value: fmt.Sprintf("<http://%s.orthanc.osimis.io|%s.orthanc.osimis.io>", customer)})
stack.SetConfig(ctx, "osimis.orthanc:config.version", auto.ConfigValue{Value: version})
In my stack, I retrieve the settings via:
const demoConfig = new pulumi.Config('osimis.orthanc').requireObject<orthanc.OrthancServiceConfig>('config')
But when running my automation program, I still have the error: error: Missing required configuration variable 'osimis.orthanc:config'
https://www.pulumi.com/docs/intro/concepts/config/#structured-configurationlimited-rainbow-51650
10/05/2020, 8:37 AMpulumi config set --path osimis.orthanc:config.name demo
limited-rainbow-51650
10/05/2020, 8:59 AM--path
at all to be found: https://github.com/pulumi/pulumi/blob/3be1ea9592b305df8aeb83c3810aee9bb8adeb7a/sdk/go/x/auto/local_workspace.go#L166-L184limited-rainbow-51650
10/06/2020, 2:50 PMnpm install
in a Setup
func on the GitRepo
setup like adviced here: https://pulumi-community.slack.com/archives/C019YSXN04B/p1600959484002700?thread_ts=1600959097.002500&cid=C019YSXN04B
The app is running using a sub-image of pulumi/pulumi-nodejs:2.11.2
. But when executing this, the npm install
bails out. When trying this manually via an attached terminal, the npm install
seems to hang around 75%. Package being installed at that moment was grcp-js
, but not sure if it is related to that. Eventually, the process is killed. sighlemon-agent-27707
10/07/2020, 7:33 AMlemon-agent-27707
10/08/2020, 7:47 PMsalmon-account-74572
10/08/2020, 7:51 PMbillowy-army-68599
10/08/2020, 8:50 PMlemon-agent-27707
10/08/2020, 10:36 PMlemon-agent-27707
10/09/2020, 2:20 AM.apply
call:gifted-student-18589
10/09/2020, 9:40 AMgifted-student-18589
10/09/2020, 9:44 AMawait stack.workspace.installPlugin("aws", "v3.6.1");
, this looks promising already.famous-kite-52506
10/13/2020, 1:28 PMlemon-agent-27707
10/14/2020, 10:14 PMlemon-agent-27707
10/19/2020, 4:30 PMboundless-insurance-52858
10/19/2020, 6:06 PMboundless-insurance-52858
10/19/2020, 6:08 PMprehistoric-librarian-12686
10/20/2020, 7:59 AMpulumi
command and now with automation api - pulumi
command itself is a lib call and can be wrapped over custom REST APIs to abstract the infra management process?prehistoric-librarian-12686
10/20/2020, 10:35 AMThe CDK for Terraform project helps users define infrastructure resources using supported programming languages and generates a Terraform configuration in JSON
But in case of Pulumi - there is no interim DSL generated right? So the infra deployment capability is provided by the lib as a feature and does not need an extra step of running the deployer i.e. to do a pulumi up
or terraform apply
prehistoric-librarian-12686
10/21/2020, 3:59 AMlemon-agent-27707
10/24/2020, 6:22 AMcurved-pharmacist-41509
11/02/2020, 11:55 PMbrief-alligator-51254
11/03/2020, 11:27 AMfancy-jelly-61092
11/03/2020, 3:47 PMextends pulumi.dynamic.Resource
) in a nodejs inline program using the Automation API? I get an exception: Error: Cannot find module '@pulumi/pulumi/cmd/dynamic-provider'
as well as error: could not read plugin [C:\Users\barcl\.pulumi\bin\pulumi-resource-pulumi-nodejs.cmd] stdout: EOF
. The installation works perfectly well using the traditional CLI-driven methodhundreds-musician-51496
11/04/2020, 1:32 AMrefresh()
on a stack that doesn't exist, what happens? Is that an error or no-op? (Using TypeScript if it matters)curved-pharmacist-41509
11/04/2020, 12:21 PMup
?hundreds-musician-51496
11/04/2020, 6:15 PMError: Program run without the Pulumi engine available; re-run using the `pulumi` CLI
at requireTestModeEnabled (C:\Users\Justin\Source\foo\internal-docs\deploy\node_modules\@pulumi\pulumi\runtime\settings.js:108:15)
at Object.getMonitor (C:\Users\Justin\Source\foo\internal-docs\deploy\node_modules\@pulumi\pulumi\runtime\settings.js:190:13)
at Object.readResource (C:\Users\Justin\Source\foo\internal-docs\deploy\node_modules\@pulumi\pulumi\runtime\resource.js:48:32)
at new Resource (C:\Users\Justin\Source\foo\internal-docs\deploy\node_modules\@pulumi\pulumi\resource.js:204:24)
at new CustomResource (C:\Users\Justin\Source\foo\internal-docs\deploy\node_modules\@pulumi\pulumi\resource.js:303:9)
at new StackReference (C:\Users\Justin\Source\foo\internal-docs\deploy\node_modules\@pulumi\pulumi\stackReference.js:44:9)
at C:\Users\Justin\Source\foo\internal-docs\deploy\index.ts:64:193
at Generator.next (<anonymous>)
at C:\Users\Justin\Source\foo\internal-docs\deploy\index.ts:8:71
at new Promise (<anonymous>)
I'm sure i'm missing something obvious. (thread)hundreds-musician-51496
11/04/2020, 8:14 PMhundreds-musician-51496
11/04/2020, 10:19 PMaws.lambda.CallbackFunction
) are resolving to undefined
inside apply
. Why would that be? (thread)hundreds-musician-51496
11/04/2020, 10:19 PMaws.lambda.CallbackFunction
) are resolving to undefined
inside apply
. Why would that be? (thread)directoryRetryHandler = new aws.lambda.CallbackFunction(`...`, {
...
}),
docsDistribution = new aws.cloudfront.Distribution(`...`, {
defaultCacheBehavior: {
...
lambdaFunctionAssociations: [{
eventType: "origin-response",
lambdaArn: pulumi.interpolate`${directoryRetryHandler.arn}:${directoryRetryHandler.version}`,
}]
}
}),
When I try to bring the stack up, AWS complains:
error creating CloudFront Distribution: InvalidLambdaFunctionAssociation: Invalid function ARN: undefined:undefined
lemon-agent-27707
11/04/2020, 10:29 PMhundreds-musician-51496
11/04/2020, 10:31 PM