-
Notifications
You must be signed in to change notification settings - Fork 367
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
S3 with Bucket Policy will stuck with reason "Creating" state #1771
Labels
bug
Something isn't working
Comments
1 task
2 tasks
I tested it with the example above and it seems like the issue is caused by AWS converting bools in conditions to strings: policy.Policy{
Version: "2012-10-17",
ID: "",
Statements: policy.StatementList{
{SID: "DenyIncorrectEncryptionHeader", Effect: "Deny", Principal: &{AllowAnon: true}, Action: {"s3:PutObject"}, ...},
{
... // 6 identical fields
Resource: {"arn:aws:s3:::test-bucket-mfqjc-hnx2w-asdas/*"},
NotResource: nil,
- Condition: policy.ConditionMap{"Null": {"s3:x-amz-server-side-encryption": bool(true)}},
+ Condition: policy.ConditionMap{"Null": {"s3:x-amz-server-side-encryption": string("true")}},
},
{SID: "AllowTenantReadWrite", Effect: "Allow", Principal: &{AllowAnon: true}, Action: {"s3:GetBucketLocation", "s3:GetBucketVersioning", "s3:GetLifecycleConfiguration", "s3:GetObject", ...}, ...},
{
... // 6 identical fields
Resource: {"arn:aws:s3:::test-bucket-mfqjc-hnx2w-asdas", "arn:aws:s3:::test-bucket-mfqjc-hnx2w-asdas/*"},
NotResource: nil,
- Condition: policy.ConditionMap{"Bool": {"aws:SecureTransport": bool(false)}},
+ Condition: policy.ConditionMap{"Bool": {"aws:SecureTransport": string("false")}},
},
},
} |
Thanks @MisterMX , i have tested with provider-aws v0.41.0 In my Bucket composition, i have to convert the conditions to making use of stringValue instead to make it works, not sure if this is the intention
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
What happened?
This issue is related to : #1758 (comment)
How can we reproduce it?
Create S3 with Bucket Policy, the state will stuck with reason "Creating" state. Please refer to existing issue in #1758
What environment did it happen in?
Crossplane version: 1.10.1
Provider-aws version: master build (last commit: 8282408)
Kubernetes version: v1.24.13-eks-0a21954
This is my sample Bucket manifest created from composition
The text was updated successfully, but these errors were encountered: