This message was deleted.

Are you using a Pulumi BucketObject? Or just uploading the file? If you're using a single BucketObject and calling

pulumi up

to update it, you can add a

dependsOn

opt.

Hey tenwit 🙂 I’ll try to grab the relevant code:

const code = new aws.s3.BucketObject(..)
new aws.kinesisanalyticsv2.Application('...', {
  applicationConfiguration: {
    applicationCodeConfiguration: {
      codeContentType: 'ZIPFILE',
      codeContent: {
        s3ContentLocation: {
          bucketArn: datalake.bucket.arn,
          fileKey: code.key,
        },
      },
    },
})

So if you're changing the code locally and uploading it using that BucketObject, then add a

dependsOn: code

to the 3rd parameter to

new Application(name, args, opts)

so when i update the code behind the bucket object, it actually does update the kinesis application as well, e.g.

updated (14s)    [diff: ~applicationConfiguration]

But - and this may be a AWS issue - the application continues to exhibit bugs that were fixed in the new code, and I need to manually make some changes in AWS console to get the new code to be accepted

Ah, no, it's already dependent because of that key.

I copy the s3 bucket object and add a number to the end, then go into kinesis apps and press ‘configure’ to change the code location

If that's how Kinesis needs to be configured, then that's what you have to do in Pulumi. Can you not get Kinesis to always use the same object? Or does it have to use a different object for every update?

ok I’ll try to do some more testing and see if I can create a reproduction repo