shy-whale-9556
05/22/2024, 3:32 PMlively-crayon-44649
05/22/2024, 3:48 PMdependsOn
achieve what you want?shy-whale-9556
05/22/2024, 3:52 PMlively-crayon-44649
05/22/2024, 3:54 PMlively-crayon-44649
05/22/2024, 3:55 PMpulumi refresh
, which instructs Pulumi to look at all cloud resources and update its state accordinglyshy-whale-9556
05/22/2024, 3:56 PMshy-whale-9556
05/22/2024, 3:59 PMconst resource1 = new aws.Resource("resource1", { property: value })
if (resource1.isDirty()) {
// force resource2 to update
}
though i can't find any such runtime method to determine that resource1 is set to be updatedlively-crayon-44649
05/22/2024, 4:04 PMshy-whale-9556
05/22/2024, 4:04 PMshy-whale-9556
05/22/2024, 4:04 PMlively-crayon-44649
05/22/2024, 4:05 PMshy-whale-9556
05/22/2024, 4:05 PMlively-crayon-44649
05/22/2024, 4:05 PMpulumi.Command
there is triggers
but that is specific to that resourceshy-whale-9556
05/22/2024, 4:11 PMlively-crayon-44649
05/22/2024, 4:22 PMorange-policeman-59119
05/23/2024, 3:14 PMgreat-sunset-355
05/24/2024, 6:20 AMintialize
method which is not properly documented here: https://github.com/pulumi/docs/issues/11432shy-whale-9556
05/29/2024, 3:03 AMreplaceOnChanges
is definitely the surface area i'm looking to attack. but apart from doing something really heavy handed like sha-ing the entire configuration for resourceA
and injecting the hash in to the description field for resourceB
or whatever, there is no mechanism i can devise to ensure that the replaceOnChanges
field i'm targeting updates if and only if resourceA
will be created or updatedorange-policeman-59119
05/29/2024, 3:05 AMshy-whale-9556
06/03/2024, 3:58 PMaws-native
as aws
has publish: true
directly on the lambda resource which works great. but with aws-native
, the lambda and lambda version being 2 separate resources means it only publishes the initial version, then does not create a new version unless the version resource itself is updated, whereas i need a new version to be created every time any property of the lambda changes (an environment variable, say)orange-policeman-59119
06/03/2024, 4:12 PMaws_native.lambda.Function
you pass it in a changing zipFile or other code, but it is a separate aws_native.lambda.Version
resource that creates a new instance using the current code of the lambda.
Would you be able to switch to using the aws
package's lambda function? It seems like it'll be better behaved. In the mean time I'll flag this issue with the providers team that owns AWS Native for them to create an issue.orange-policeman-59119
06/03/2024, 10:34 PMaws.lambda.Function
instead of the AWS Native implementation, as it does what you want on handling version updates.
The AWS Native provider implements the CloudControl & CloudFormation API from AWS, and in this case it results in a very hard to use set of resources.