Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

‼️(s3_deployment): SourceMarker removed in 2.55.0 breaking deployment #23357

Closed
tenjaa opened this issue Dec 15, 2022 · 3 comments
Closed
Assignees
Labels

Comments

@tenjaa
Copy link
Contributor

tenjaa commented Dec 15, 2022

Describe the bug

After updating from 2.54.0 to 2.55.0 my deployment using the s3_deployment breaks with the error message:

'source_markers' and 's3_source_zips' must be the same length

Expected Behavior

When deploying with the new cdk version, I do not want to see a diff.

npx cdk diff with 2.54.0:

[~] Custom::CDKBucketDeployment Dashboard/WebsiteDeployment/CustomResource-c8eefc42ee0a23e7a1eaf8eee51ca8f6c7d2f8554e DashboardWebsiteDeploymentCustomResourcec8eefc42ee0a23e7a1eaf8eee51ca8f6c7d2f8554eA9ADAAAE 
 └─ [~] SourceObjectKeys
     └─ @@ -1,4 +1,4 @@
        [ ] [
        [-]   "d87aa38409ea881a0b0710cac75785074770247efc260c6e38d93ab1cd78de16.zip",
        [+]   "583dcc9b108a4f41ddf685568c9e24869a603da5ad69808ba60cd1adf36d7139.zip",
        [ ]   "d6c6d61e45fa377ee62f1c19899768187aea505cdf161f967ed9fea2d54466cd.zip"
        [ ] ]

Current Behavior

npx cdk diff with 2.55.0:

[~] Custom::CDKBucketDeployment Dashboard/WebsiteDeployment/CustomResource-c8eefc42ee0a23e7a1eaf8eee51ca8f6c7d2f8554e DashboardWebsiteDeploymentCustomResourcec8eefc42ee0a23e7a1eaf8eee51ca8f6c7d2f8554eA9ADAAAE 
 ├─ [~] SourceMarkers
 │   └─ @@ -1,4 +1,3 @@
 │      [ ] [
 │      [-]   {},
 │      [ ]   {}
 │      [ ] ]
 └─ [~] SourceObjectKeys
     └─ @@ -1,4 +1,4 @@
        [ ] [
        [-]   "d87aa38409ea881a0b0710cac75785074770247efc260c6e38d93ab1cd78de16.zip",
        [+]   "583dcc9b108a4f41ddf685568c9e24869a603da5ad69808ba60cd1adf36d7139.zip",
        [ ]   "d6c6d61e45fa377ee62f1c19899768187aea505cdf161f967ed9fea2d54466cd.zip"
        [ ] ]

Reproduction Steps

    new BucketDeployment(this, 'WebsiteDeployment', {
      vpc: props.vpc,
      destinationBucket: websiteBucket,
      sources: [
        Source.asset(path.join(__dirname, '../../frontend'), {
          bundling: {
            image: DockerImage.fromRegistry('public.ecr.aws/docker/library/node'),
            local: {
              tryBundle(outputDir: string) {
                const buildScriptPath = path.join(__dirname, '../../build-frontend.sh');
                spawnSync(`sh`, [buildScriptPath, outputDir]);
                return true;
              },
            },
          },
        }),
        Source.jsonData('licenses.json', licenses),
      ],
    });

Possible Solution

No response

Additional Information/Context

It looks like the issue is introduced by b34d0b7

CDK CLI Version

2.55.0

Framework Version

No response

Node.js Version

18.x

OS

osx

Language

Typescript

Language Version

No response

Other information

No response

@tenjaa tenjaa added bug This issue is a bug. needs-triage This issue or PR still needs to be triaged. labels Dec 15, 2022
@MrArnoldPalmer
Copy link
Contributor

Hey there, thanks for the report. Working on getting a fix out #23364

@MrArnoldPalmer MrArnoldPalmer added p0 and removed needs-triage This issue or PR still needs to be triaged. labels Dec 15, 2022
@MrArnoldPalmer MrArnoldPalmer changed the title (s3_deployment): SourceMarker removed in 2.55.0 breaking deployment NOTICE!! (s3_deployment): SourceMarker removed in 2.55.0 breaking deployment Dec 15, 2022
@MrArnoldPalmer MrArnoldPalmer pinned this issue Dec 15, 2022
@MrArnoldPalmer MrArnoldPalmer changed the title NOTICE!! (s3_deployment): SourceMarker removed in 2.55.0 breaking deployment ‼️(s3_deployment): SourceMarker removed in 2.55.0 breaking deployment Dec 15, 2022
@MrArnoldPalmer
Copy link
Contributor

Anyone who runs into this please upgrade to v2.55.1 as it includes the fix above.

@github-actions
Copy link

⚠️COMMENT VISIBILITY WARNING⚠️

Comments on closed issues are hard for our team to see.
If you need more assistance, please either tag a team member or open a new issue that references this one.
If you wish to keep having a conversation with other community members under this issue feel free to do so.

@khushail khushail unpinned this issue Jan 10, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

3 participants