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 PMmillions-furniture-75402
05/21/2020, 3:59 PMbest-lifeguard-91445
05/21/2020, 4:48 PMaws.sqs.QueuePolicy
with a dynamic list of statements? I'm getting: Calling [toString] on an [Output<T>] is not supported.
function createQueuePolicyStatement(inboundSqs: aws.sqs.Queue, topicData: TopicData[]): pulumi.Input<string> {
const statement = (queueArn: Output<string>, topicArn: Output<string>) => {
return queueArn.apply((qarn) => {
return topicArn.apply((tarn) => {
return `
{
"Effect": "Allow",
"Principal": "*",
"Action": "SQS:SendMessage",
"Resource": "${qarn}",
"Condition": {
"ArnEquals": {
"aws:SourceArn": "${tarn}"
}
}`
});
});
}
const policyStatement = `
"Version": "2012-10-17",
"Id": "sqspolicy",
"Statement": [
${topicData.map((data) => statement(inboundSqs.arn, data.topic.arn)).join(`,`)}
]
}`;
return policyStatement;
}
dazzling-memory-8548
05/21/2020, 6:49 PMparquetjs
) that has a compiled sub-dependency (lzo
). We've now noticed that every time we rebuild our node_modules
directory (with npm ci
), the hash of the compiled lzo
module changes, causing pulumi to want to redeploy all of our lambdas (even though no deps have actually changed).
Is there an elegant workaround to prevent pulumi from continuously redeploying our lambdas? We've already tried excluding lzo
in codePathOptions
.
cc @worried-engineer-33884wonderful-dog-9045
05/21/2020, 7:01 PMcool-egg-852
05/21/2020, 8:05 PMprovider
with it’s children? I’m having an issue with a setup such as:
Monitors (ComponentResource) (provider set)
Monitor (ComponentResource)
datadog.Monitor
The datadog.Monitor
doesn’t seem to have it’s provider
set as far as I can tell. I was under the impression that the provider
should be on it.best-lifeguard-91445
05/22/2020, 3:15 AMkind-mechanic-53546
05/22/2020, 4:42 AMgreen-salesclerk-34937
05/22/2020, 6:19 AMgreen-salesclerk-34937
05/22/2020, 6:20 AMmaxSize
in cluster optgray-carpet-67751
05/22/2020, 8:12 AM2020-05-22T08:04:50.9212982Z error: no stack named 'dfds-frontend/production' found
2020-05-22T08:04:50.9944971Z error: --yes must be passed in to proceed when running in non-interactive mode
2020-05-22T08:04:51.0637194Z error: --yes must be passed in to proceed when running in non-interactive mode
2020-05-22T08:04:51.5013922Z error: no stack selected; please use `pulumi stack select` to choose one
This stack actually exists and it worked like a week ago but for some reaso it's been failing for a few days. Any pointers you could give me?prehistoric-gold-59191
05/22/2020, 9:54 AMincalculable-army-40859
05/22/2020, 2:08 PMhelm.v2
module. Does use Helm 3 or Helm 2?clever-plumber-29709
05/22/2020, 5:26 PMbest-lifeguard-91445
05/22/2020, 6:03 PMpulumi up
successfully, subsequent runs are producing this error:
~ ├─ aws:rds:Cluster rds-cluster-patient-access-prod **updating failed** [diff: ~availabilityZones]; 1 error
├─ aws:autoscaling:Group app-services **failed** 1 error
└─ aws:autoscaling:Group edge-services **failed** 1 error
Diagnostics:
aws:autoscaling:Group (app-services):
error: transport is closing
aws:autoscaling:Group (edge-services):
error: transport is closing
aws:rds:Cluster (rds-cluster-patient-access-prod):
error: transport is closing
pulumi:pulumi:Stack (aws-prod):
error: update failed
panic: fatal: An assertion has failed: Expected diff to not require deletion or replacement during Update of urn:pulumi:prod::aws::aws:rds/cluster:Cluster::rds-cluster-patient-access-prod
I'm not making any changes to the cluster or related resources (availability zones, auto scaling groups).. any ideas?billowy-nightfall-59212
05/22/2020, 6:48 PMpulumi
for more than a year. Please DM, if you are hiring. Thanksbillowy-nightfall-59212
05/22/2020, 6:48 PMpulumi
for more than a year. Please DM, if you are hiring. Thanks