fancy-flower-77794
07/13/2021, 1:22 AMmany-yak-61188
07/13/2021, 7:28 AMconst asgEventsTopic = new aws.sns.Topic("asg-events-topic")
asgEventsTopic.onEvent("ci-cd-scale-in", async ev =>{
console.log("Processing " + ev);
})
const runnerAsg = new aws.autoscaling.Group("ci-cd-runner-asg", {
name: "ci-cd-runner-asg",
desiredCapacity: 2,
maxSize: 2,
minSize: 1,
healthCheckGracePeriod: 300,
healthCheckType: "EC2",
launchTemplate: {
id: launchTemplate.id,
version: `$Latest`,
},
vpcZoneIdentifiers: vpc.privateSubnetIds,
initialLifecycleHooks: [{
name: "asg-events-hook",
defaultResult: "CONTINUE",
lifecycleTransition: "autoscaling:EC2_INSTANCE_TERMINATING",
notificationTargetArn: asgEventsTopic.arn
}]
});
the sns topic is assigned as a notificationTargetArn
to the ASG. I noticed during delete the topic subscription is deleted before the ASG. If it were the other way around, ASG deleted prior to topic subscription, deleting ASG would fire lifecycle transtion events for the EC2 hosts. In thread, I'm posting the output of pulumi delete
bug may be / am I missing something?nutritious-shampoo-16116
07/13/2021, 9:59 AMancient-eve-13947
07/13/2021, 10:11 AMServerArgs
parameters, too. The same goes for CosmosDb: there is the name parameter of the constructor and the AccountName
property of DatabaseAccountArgs
.
What's the deal here? Why are there two different ways of specifying the name? What happens if I don't specify the one in the properties?
Thank you,
Mark @ DEONcold-coat-35200
07/13/2021, 11:43 AMincalculable-printer-98305
07/13/2021, 2:56 PMancient-eve-13947
07/13/2021, 4:49 PMcors: [{
allowedOrigins: ["<http://www.example.com>"],
}]
but if I do that, there is a com/transpiler error:
Type '{ allowedOrigins: string[]; }[]' is not assignable to type 'Input<SignalRCorsSettingsArgs> | undefined'.
Type '{ allowedOrigins: string[]; }[]' is missing the following properties from type 'OutputInstance<SignalRCorsSettingsArgs>': apply, getts(2322)
signalR.d.ts(118, 5): The expected type comes from property 'cors' which is declared here on type 'SignalRArgs'ancient-eve-13947
07/13/2021, 4:50 PMancient-eve-13947
07/13/2021, 5:07 PMcors: {
allowedOrigins: ["http://www.example.com"],
}
would be good to adjust the docsancient-eve-13947
07/13/2021, 5:09 PMnew azure.signalr.Service
while the current way is new SignalR
bored-oyster-3147
07/13/2021, 7:34 PM--server
flag on pulumi plugin install
? Can the URL be blob storage? Is there a specific directory structure it is expecting? etc.bored-oyster-3147
07/13/2021, 8:56 PMazure-native
it generates a dotnet project sdk called Pulumi.AzureNative
instead of Pulumi.Azure-native
?calm-gpu-56173
07/14/2021, 12:01 AMfast-advantage-98237
07/14/2021, 3:01 AMComputed attributes cannot be set: Computed attributes cannot be set, but a value was set for "vpc_config.0.vpc_id".. Examine values at 'Cluster.VpcConfig.VpcId'.
fast-advantage-98237
07/14/2021, 3:01 AMmicroscopic-orange-69417
07/14/2021, 4:13 AMicy-jordan-58549
07/14/2021, 11:34 AMRun pulumi/setup-pulumi@v2
with:
pulumi-version: 3.7.0
Configured range: 3.7.0
Error: Could not find a version that satisfied the version range
ancient-eve-13947
07/14/2021, 1:31 PMcalm-gpu-56173
07/14/2021, 1:50 PMbored-oyster-3147
07/14/2021, 2:16 PMPulumi
NuGet package (see here), so the generated dotnet SDK can't build as it is. Originally I thought OK maybe the stock schema.json
is just missing an argument to add that reference, but the nodejs SDK generated from the same provider code does have the reference. So I'm wagering it was a bug potentially introduced during changes made to release azure-native
? Any thoughts on what I need to do so that the codegen adds that reference?sparse-apartment-71989
07/14/2021, 3:39 PMrough-football-77038
07/14/2021, 4:02 PMpulumi import aws:lambda/function:Function test_lambda my_test_lambda_function
but, this does not work, error:
"Preview failed: handler and runtime must be set when PackageType is Zip"
I don't have idea how set this parameters or if have other way to import a Lambda.
I hope I have explained my problem well, I appreciate any help.
Thanks!big-microphone-36818
07/14/2021, 6:16 PMnode_modules/mocha/bin/mocha -r ts-node/register index.ts
, none of the configuration values from my project’s stack are loaded. Any tips would be greatly appreciated.elegant-crayon-4967
07/14/2021, 7:00 PMsessionName
param passed in. We have conditions setup on our service accounts that only allow assume role usage if the session name matches the correct phrase. I have Pulumi setup to match this _sessionName_: 'agent-example'
but in my cloudtrail logs I can clearly see the assume role operation denied and the request parameters show as “null” where it should show the sessionName.hundreds-businessperson-87013
07/14/2021, 8:10 PMancient-eve-13947
07/15/2021, 10:25 AMminiature-leather-70472
07/15/2021, 10:26 AMproud-easter-54321
07/15/2021, 11:42 AMpulumi up
?limited-mouse-98047
07/15/2021, 1:49 PM--target-dependents
has no effect. I must be missing something here.little-market-63455
07/15/2021, 2:11 PMdestroy
. I am not using the automation API and wondering if there is a property somewhere that tells me what mode is the CLI running under like up
, destroy
, refresh
, preview
and so on. I check pulumi.runtime
but it doesn't seem to expose this. I am probably not doing it the correct way, maybe dynamic providers?little-market-63455
07/15/2021, 2:11 PMdestroy
. I am not using the automation API and wondering if there is a property somewhere that tells me what mode is the CLI running under like up
, destroy
, refresh
, preview
and so on. I check pulumi.runtime
but it doesn't seem to expose this. I am probably not doing it the correct way, maybe dynamic providers?bored-oyster-3147
07/15/2021, 2:33 PMIsDryRun
which tells you if it is preview
. That is so you can omit work that should only run during an up
. Both refresh
and destroy
don't actually execute your pulumi code so it isn't necessary to check for themlittle-market-63455
07/15/2021, 4:04 PMdestroy
for cleanup but I guess that should live elsewhere. Thanks for the tip though 👍bored-oyster-3147
07/15/2021, 4:06 PMpulumi destroy
. Because pulumi destroy
just loads your providers and destroyed what is currently in your state, which is why it doesn't execute your pulumi code