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
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion config/clusters/2i2c-aws-us/showcase.values.yaml
Original file line number Diff line number Diff line change
Expand Up @@ -4,7 +4,7 @@ basehub:
# When we renamed this hub, we did so at a DNS level and not an infrastructure
# level. No terraform config was touched. Hence the kubernetes annotations retain
# the original hub name.
eks.amazonaws.com/role-arn: arn:aws:iam::790657130469:role/2i2c-aws-us-researchdelight
eks.amazonaws.com/role-arn: arn:aws:iam::790657130469:role/2i2c-aws-us-showcase
jupyterhub:
ingress:
hosts: [showcase.2i2c.cloud]
Expand Down
2 changes: 1 addition & 1 deletion terraform/aws/projects/2i2c-aws-us.tfvars
Original file line number Diff line number Diff line change
Expand Up @@ -40,7 +40,7 @@ hub_cloud_permissions = {
bucket_admin_access : ["scratch-dask-staging"],
extra_iam_policy : ""
},
"researchdelight" : {
"showcase" : {
requestor_pays : true,
bucket_admin_access : [
"scratch-researchdelight",
Expand Down
Loading