chore(ci): remove legacy S3 deploy after CloudFront cutover (QOV-2108) - #2846
Merged
Merged
Conversation
The CloudFront origin buckets now serve console.qovery.com and console-staging.qovery.com, so the dual-target scaffolding from the migration is no longer needed: - drop the legacy bucket copy steps and the s3-bucket-name-with-cloudfront indirection; the origin bucket is now plain s3-bucket-name - make the CloudFront steps unconditional since both deploy flows set the bucket and distribution - remove the cloudflare-zone/cloudflare-token secrets, declared and passed but unused by any step
Member
|
Qovery can create a Preview Environment for this PR.
This comment has been generated from Qovery AI 🤖.
|
|
View your CI Pipeline Execution ↗ for commit a247b89
💡 Verify your cache is correct by running tasks in a sandbox. Read docs ↗ ☁️ Nx Cloud last updated this comment at |
RemiBonnet
approved these changes
Aug 4, 2026
Member
|
🎉 This PR is included in version 1.332.0 🎉 The release is available on GitHub release Your semantic-release bot 📦🚀 |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Cleanup after the CloudFront migration (QOV-2108, follow-up to #2839 and #2841). The dual-target deploy scaffolding is removed now that CloudFront serves the sites:
console-staging.qovery.com/console.qovery.combuckets are gone. The CloudFront origin buckets (qovery-console-staging/qovery-console-prod) are now the only deploy target, passed as plains3-bucket-name(thes3-bucket-name-with-cloudfrontindirection is dropped).if: env.X != ''conditions on the CloudFront steps are gone — both deploy flows always set the bucket and distribution.cloudflare-zone/cloudflare-tokenwere declared and passed but never used by any step.Test plan
console-staging.qovery.com)