s3-deployment: allow disabling "sync --delete"

The current behavior is aws sync --delete, which means that destination files that don’t exist in source will be deleted. In some scenarios (see #936) it might be useful to retain old files for the transition period when an app is updated.

[IslamWahid]

@eladb with that prune option, how will the old files be deleted eventually? it’s necessary to keep them until the deployment is done but afterwards, we still want to remove them.

[martinnabhan]

Still relevant for us too!

We’re trying to set different headers for only index.html, but currently it doesn’t seem to be possible. We’ve tried using two deployments, but since we can’t disable sync --delete it’s always one deployment or the other.

    new BucketDeployment(this, 'BucketDeployment', {
      sources: [Source.asset('../cms/dist', { exclude: ['.git', 'cdk.out', 'node_modules', 'index.html' })],
      destinationBucket: bucket,
      cacheControl: [CacheControl.fromString('max-age=31536000,public,immutable')],
    });

    new BucketDeployment(this, 'HTMLBucketDeployment', {
      sources: [Source.asset('../cms/dist', { exclude: ['**', '!index.html'] })],
      destinationBucket: bucket,
      cacheControl: [CacheControl.fromString('max-age=0,no-cache,no-store,must-revalidate')],
      contentType: 'text/html; charset=utf-8',
    });

Is there any other way of setting headers for specific objects?