kind-mechanic-53546
05/19/2020, 7:23 AMdocker.Image
but I cannot get it to pass it decrypted
Definition: _export_ const sec = pulumiConfig.requireSecret("secKey");
I've tried pulumi.all([sec]).apply(([secString]) => { return { ARG_NAME: secString }; });
and { ARG_NAME: sec.apply(v=>v) }
Neither of these works, the value is always either [secret]
or Calling [toString] on an [Output<T>] is not supported.\n\nTo get the value of an Output...
For what it's worth, pulumi.all
works fine on a secret imported from another stack using a StackReferencebillowy-jackal-69220
05/19/2020, 7:54 AMpreview
stage to feed that into up
or is there any other way to implement a review stage in CI without the posibility of a drift in the infrastructure in the mean time?limited-carpenter-34991
05/19/2020, 8:23 AMbest-hospital-12760
05/19/2020, 11:01 AMpulumi.yaml
and pulumi-stackname.yaml
.
starting a thread so I don't turn general into pastebin 😄millions-furniture-75402
05/19/2020, 2:03 PM@pulumi/
recursively, so even if I specify pulumi.runtimeDependencies
in package.json, they’ll be removed.
• https://www.pulumi.com/docs/tutorials/aws/serializing-functions/#determining-the-appropriate-node-modules-packages-to-include-with-a-lambda
• https://github.com/pulumi/pulumi/blob/master/sdk/nodejs/runtime/closure/codePaths.ts#L296-L300
Being able to run the lambda with the mysql provider would be preferred, but it seems I’m forced to look into other possible solutions, which are more complex.
Other Possible Solutions:
1. Publish a lambda with an external tool, and call it as an existing lambda with pulumi (messy, requires more than pulumi up
).
2. Use mysql nodejs package to create the database (that stinks, I have a MySQL provider).
3. In addition to GitHub Actions, use AWS Code Services so the pipeline can run in the VPC (redundant).
4. Run either a mysql, or pulumi container in fargate that can provision the databases (seems like a lot more infra and complexity to create databases).
Maybe I’m missing something obvious here. Hoping someone can shed some light on how I should approach this problem, and maybe other opportunities I’ve overlooked. Thanks, loving Pulumi so far!big-potato-91793
05/19/2020, 4:03 PMnode-pre-gyp WARN Using needle for node-pre-gyp https download
node-pre-gyp WARN Pre-built binaries not installable for grpc@1.24.2 and node@12.16.3 (node-v72 ABI, glibc) (falling back to source compile with node-gyp)
node-pre-gyp WARN Hit error bad download
gyp WARN EACCES current user ("pulumi") does not have permission to access the dev dir "/root/.cache/node-gyp/12.16.3"
That increase the deployment time. I’m using the latest pulumi container image… any idea?best-lifeguard-91445
05/19/2020, 5:36 PMbreezy-hamburger-69619
05/19/2020, 7:01 PMlimited-carpenter-34991
05/19/2020, 7:28 PMbest-lifeguard-91445
05/19/2020, 7:41 PMreturn new awsx.ecs.EC2Service("myservice", {
cluster,
subnets: service.subnets,
taskDefinitionArgs: {
vpc,
networkMode: "awsvpc",
containers: [
"myContainer": { image: '...',
networkListener = {
port: 80,
sslPolicy: 'ELBSecurityPolicy-TLS-1-2-Ext-2018-06'
}
}
],
}
...
}
echoing-breakfast-73834
05/19/2020, 9:01 PM--code-path "/some/path"
argument? Didn't see one in the docs.bland-shoe-75993
05/19/2020, 11:04 PMvictorious-gigabyte-4729
05/20/2020, 5:49 AMpulumi config refresh
to pull the config down from Pulumi - or maybe pulumi config set
for every value in the config from environment variables.
Are there any other approaches?agreeable-machine-73141
05/20/2020, 6:43 AMOutput<string>
variable? I retrieve the region as type Output<string>
which I want to use as prefix in the bucket name. I want to either convert it to string
or use the Output<string>
directly in the bucket creation. I tried the apply
and interpolate
syntax but I can’t figure out how to use correctly.
const region = pulumi.output(aws.getRegion()).name;
`const devDataBucket = new aws.s3.Bucket(${region}-dev-data
);`
Appreciate the help!full-dress-10026
05/20/2020, 3:13 PMcoalesce.go:199: warning: destination for podLabels is a table. Ignoring non-table value <nil>
coalesce.go:199: warning: destination for podLabelsAsTags is a table. Ignoring non-table value <nil>
coalesce.go:199: warning: destination for podLabels is a table. Ignoring non-table value <nil>
coalesce.go:199: warning: destination for podLabelsAsTags is a table. Ignoring non-table value <nil>
echoing-breakfast-73834
05/20/2020, 3:25 PM--silent
to the curl tarball download line? I can create a PR for this if it's in a public repo somewhereabundant-airplane-93796
05/20/2020, 4:31 PMancient-mouse-86780
05/20/2020, 5:11 PMsparse-intern-71089
05/20/2020, 5:18 PMbrainy-secretary-10332
05/20/2020, 6:29 PMerror: resource 'urn:pulumi:dev::<OMITTED>::pulumi:pulumi:StackReference::<OMITTED>/<OMITTED>/dev' registered twice (read and read)
I'm not sure what I would need to do next to remedy this error. Any help would be greatly appreciated.stocky-motorcycle-65008
05/20/2020, 6:49 PMincalculable-engineer-92975
05/20/2020, 8:54 PMbest-lifeguard-91445
05/20/2020, 9:03 PMmammoth-night-22453
05/20/2020, 9:31 PMbest-lifeguard-91445
05/20/2020, 9:35 PMincalculable-army-40859
05/21/2020, 1:32 AMuseIpAliases
is missing from ipAllocationPolicy
when creating a gcp.container.Cluster
. If I leave an empty ipAllocationPolicy
the cluster is not VPC-native. The property is also missing from the docs. According to the Google documentation, creating a VPC-native cluster can be achieved with:
{
"name": cluster-name,
"description": description,
...
"ipAllocationPolicy": {
"useIpAliases": true,
"createSubnetwork": true,
"subnetworkName": subnet-name
},
...
}
where ipAllocationPolicy
is described in https://cloud.google.com/kubernetes-engine/docs/reference/rest/v1/projects.locations.clusters#Cluster.IPAllocationPolicy.icy-napkin-56528
05/21/2020, 8:44 AMbroad-dog-22463
05/21/2020, 10:27 AMmillions-furniture-75402
05/21/2020, 1:47 PMastonishing-quill-88807
05/21/2020, 3:15 PM