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

2i2c-aws-us, showcase: fix bucket access after rename #3663

Merged

Conversation

consideRatio
Copy link
Contributor

@consideRatio consideRatio commented Jan 31, 2024

Fixes #3639 reported by @jnywong via freshdesk. There are some some debugging notes on how I arrived at this fix detailed in #3639 (comment).

@consideRatio consideRatio requested a review from a team as a code owner January 31, 2024 12:01
Copy link

Merging this PR will trigger the following deployment actions.

Support and Staging deployments

Cloud Provider Cluster Name Upgrade Support? Reason for Support Redeploy Upgrade Staging? Reason for Staging Redeploy
aws 2i2c-aws-us No Yes Following prod hubs require redeploy: showcase

Production deployments

Cloud Provider Cluster Name Hub Name Reason for Redeploy
aws 2i2c-aws-us showcase Following helm chart values files were modified: showcase.values.yaml

@consideRatio consideRatio merged commit 640b904 into 2i2c-org:master Jan 31, 2024
9 of 10 checks passed
@consideRatio
Copy link
Contributor Author

Thanks @GeorgianaElena for instant review :)

Copy link

🎉🎉🎉🎉

Monitor the deployment of the hubs here 👉 https://github.com/2i2c-org/infrastructure/actions/runs/7725746511

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
No open projects
Status: Done 🎉
Development

Successfully merging this pull request may close these issues.

How to write to scratch and persistent buckets on a hub?
2 participants