-
Notifications
You must be signed in to change notification settings - Fork 67
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
[showcase] Add a persistent bucket #3628
[showcase] Add a persistent bucket #3628
Conversation
I got more changes than I expected here Output of terraform plan
|
I think this is benign and a consequence of how things are written in terraform. Overview of changesThe terraform changes can be overviewed as three parts: Resources are created
Data is read
Resources are maybe changed Note the # aws_s3_bucket_policy.user_bucket_access["dask-staging.scratch-dask-staging"] will be updated in-place
~ resource "aws_s3_bucket_policy" "user_bucket_access" {
id = "2i2c-aws-us-scratch-dask-staging"
~ policy = jsonencode(
{
- Statement = [
- {
- Action = "s3:*"
- Effect = "Allow"
- Principal = {
- AWS = "arn:aws:iam::790657130469:role/2i2c-aws-us-dask-staging"
}
- Resource = [
- "arn:aws:s3:::2i2c-aws-us-scratch-dask-staging/*",
- "arn:aws:s3:::2i2c-aws-us-scratch-dask-staging",
]
- Sid = ""
},
]
- Version = "2012-10-17"
}
) -> (known after apply)
# (1 unchanged attribute hidden)
} I opened #3632 about this, I'm fairly confident the "data is read" and "resources are maybe changed" parts are benign and don't think further review if they are is required. |
Merging this PR will trigger the following deployment actions. Support and Staging deployments
Production deployments
|
I have deployed this:
I shall merge this now |
🎉🎉🎉🎉 Monitor the deployment of the hubs here 👉 https://github.com/2i2c-org/infrastructure/actions/runs/7624916948 |
requested in https://2i2c.freshdesk.com/a/tickets/1255