Skip to content

fix(pipeline): correct usage for qualifier in diffBucket url #760

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

Closed
wants to merge 3 commits into from

Conversation

richardkeit
Copy link
Contributor

@richardkeit richardkeit commented Apr 11, 2025

closes #753

image

Worth also giving attention to (as I also disabled this to get the external deployment working):

@richardkeit richardkeit marked this pull request as ready for review April 11, 2025 03:10
)}/s3/buckets/${this.props.prefixes.bucketName}-pipeline-${cdk.Stack.of(this).account}-${
cdk.Stack.of(this).region
}?prefix=AWSAccelerator-Pipel/Diffs/#{codepipeline.PipelineExecutionId}/&region=${
)}/s3/buckets/${this.pipeline.artifactBucket.bucketName}?prefix=AWSAccelerator-Pipel/Diffs/#{codepipeline.PipelineExecutionId}/&region=${
Copy link
Contributor Author

@richardkeit richardkeit Apr 11, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

While I've corrected the incorrect naming of the bucket - the following use of #{codepipeline.PipelineExecutionId} doesn't seem to work (in external deployment account or similar) in this view (likely should go to the service team)

See hyperlink URL bottom of screenshot
Screenshot 2025-04-11 at 4 03 02 pm

But works in this view:
Screenshot 2025-04-11 at 4 09 35 pm

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Great eye, I saw the same behavior but clicking the link still directed me to the correct location in S3.

@erwaxler
Copy link
Contributor

Hey @richardkeit , thanks for submitting this! I was able to reproduce the issue and can confirm it was resolved by your fix, I will merge this code in and make sure its available in our next major release. I will take a look at #754 as well, I am still completing some additional testing there. Thanks for your support of the LZA!

@erwaxler erwaxler closed this Apr 18, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Bootstrap stage failure when deploying from external pipeline account - upload failed (NoSuchBucket)
2 participants