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

fix(s3.bucket): Fixes #1165, discrepancy QueueConfiguration.Filter.Ke… #1389

Conversation

schroeder-paul
Copy link
Contributor

Description of your changes

The AWS API returns QueueConfiguration.Filter.Key.FilterRules.Name as "Prefix"/"Suffix" but expects "prefix"/"suffix", this leads to inconsistency and a constant diff.

Privious MR would panic if some or all of the keys (e.g. Key or Filter) are not there. This additon handles these cases. Additional tests for these cases were added.

Fixes #1165

I have:

  • Read and followed Crossplane's contribution process.
  • Run make reviewable test to ensure this PR is ready for review.

How has this code been tested

Test were added, see diff.

@schroeder-paul schroeder-paul force-pushed the fix-aws-returning-Prefix-instead-of-prefix branch from 228e351 to 7164ded Compare July 19, 2022 14:00
…guration.Filter.Key.FilterRules.Name (with extensive corner case testing)

Signed-off-by: Paul Schroeder <97968850+schroeder-paul@users.noreply.github.com>
@schroeder-paul schroeder-paul force-pushed the fix-aws-returning-Prefix-instead-of-prefix branch from 7164ded to 6d56d23 Compare July 19, 2022 14:27
@schroeder-paul schroeder-paul marked this pull request as ready for review July 19, 2022 14:43
Copy link
Member

@haarchri haarchri left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@haarchri haarchri merged commit 6a6346c into crossplane-contrib:master Jul 23, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

S3 Bucket constantly calls PutBucketNotification
2 participants