millions-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. Thankschilly-hairdresser-56259
05/22/2020, 9:05 PMbest-lifeguard-91445
05/22/2020, 9:41 PMgreat-byte-67992
05/23/2020, 4:36 AMwitty-spring-28765
05/23/2020, 9:54 AMable-beard-29160
05/23/2020, 11:43 AMwonderful-dog-9045
05/23/2020, 11:48 AMable-beard-29160
05/23/2020, 6:04 PMpulumi.StackReference
work with anything else other than the Pulumi service? I'm not sure what to pass as a stack name to the constructor.green-school-95910
05/24/2020, 4:22 AM--replace
option and the only way I could find to get the urn of a resource without having to change the code was to inspect the state using pulumi stack export
green-school-95910
05/24/2020, 4:32 AMastonishing-gpu-37274
05/24/2020, 7:36 AMerror: Error creating Lambda function: ResourceConflictException: Function already exist: ****-8d56ff7
{
RespMetadata: {
StatusCode: 409,
RequestID: "a4e2508b-7d19-43cc-93db-e08b1f64914e"
},
Message_: "Function already exist: ***-8d56ff7",
Type: "User"
}
I tried using --refresh, recreating the stack, switching to a different account.
The lambda is actually created even when this error occur
Looking at the AWS cloudtrail events, I see that CreateFunction is called twice, with a 2 min difference(the time it takes to create it).
Using the latest pulumi version, anyone knows how to resolve? As a workaround I'm quickly deleting the lambda before the 2nd time it creates it, and that seems to make the pulumi update finish successfullyblue-businessperson-90950
05/24/2020, 8:52 AMblue-businessperson-90950
05/24/2020, 8:53 AMblue-businessperson-90950
05/24/2020, 8:54 AMalert-restaurant-79151
05/24/2020, 2:30 PMbrainy-psychiatrist-41826
05/24/2020, 5:37 PMgo mod vendor
, but the GH action always refetches the deps