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

#868 Fix broken handling of errors after aws-sdk-v2 migration #871

Merged

Conversation

larhauga
Copy link
Contributor

@larhauga larhauga commented Oct 12, 2021

Description of your changes

Fixes #868

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

Tested ec2.SecurityGroup, ECR.Repository, ECR.RepositoryPolicy and S3.Bucket.

Tested ok in our environment with a fork, where it previously failed.
We are not running all the affected types, so not every change has been thoroughly tested.

Copy link
Member

@muvaf muvaf left a comment

Choose a reason for hiding this comment

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

Thank you @larhauga !

pkg/clients/ec2/address.go Show resolved Hide resolved
pkg/clients/ec2/vpccidrblock.go Show resolved Hide resolved
pkg/clients/s3/bucket.go Outdated Show resolved Hide resolved
Copy link
Member

@muvaf muvaf left a comment

Choose a reason for hiding this comment

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

LGTM! @chlunde feel free to merge once your comments are addressed.

@larhauga larhauga force-pushed the aws-sdk-v2-errortypes branch from eb16745 to f4c8535 Compare October 13, 2021 11:51
@chlunde chlunde merged commit 4c3e9b2 into crossplane-contrib:master Oct 13, 2021
@chlunde chlunde deleted the aws-sdk-v2-errortypes branch October 13, 2021 12:50
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.

[showstopper] Some error checks are broken with v2 migration
3 participants