-
Notifications
You must be signed in to change notification settings - Fork 132
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 empty TypeMeta while running API conversions #1422
Fix empty TypeMeta while running API conversions #1422
Conversation
This provider repo does not have enough maintainers to address every pull request. Since there has been no activity in the last 90 days it is now marked as |
/fresh |
e675588
to
d5405cb
Compare
/test-examples="examples/ec2/v1beta2/vpcendpoint.yaml" |
/test-examples="examples/rds/v1beta2/instance.yaml" |
/test-examples="examples/ec2/v1beta1/vpcendpoint.yaml" |
/test-examples="examples/rds/v1beta1/instance.yaml" |
/test-examples="examples/ec2/v1beta1/vpcendpoint.yaml" |
f1fb3cc
to
4111162
Compare
/test-examples="examples/rds/v1beta1/instance.yaml" |
/test-examples="examples/ec2/v1beta1/vpcendpoint.yaml" |
e1a13e0
to
6e73be5
Compare
/test-examples="examples/ssm/v1beta2/maintenancewindowtask.yaml" Turns out, this resource wasn't Uptestable. |
6e73be5
to
f68c6a6
Compare
- Fix an issue with API conversions when the TypeMeta information has been dropped. - Add v1beta1 -> v1beta3 field renaming conversions for relevant resources (fast-tracked in commit 32ce2a9). - Do not replace but append conversion functions (fast-tracked in commit 32ce2a9). Signed-off-by: Alper Rifat Ulucinar <ulucinar@users.noreply.github.com>
Signed-off-by: Cem Mergenci <cmergenci@gmail.com>
Signed-off-by: Cem Mergenci <cmergenci@gmail.com>
f68c6a6
to
5d1a3b2
Compare
/test-examples="examples/rds/v1beta1/instance.yaml" |
/test-examples="examples/rds/v1beta2/instance.yaml" |
/test-examples="examples/ec2/v1beta1/vpcendpoint.yaml" |
/test-examples="examples/ec2/v1beta2/vpcendpoint.yaml" |
/test-examples="examples/s3/v1beta1/bucket.yaml" |
/test-examples="examples/firehose/v1beta2/deliverystream.yaml" |
/test-examples="examples/eks/v1beta2/nodegroup.yaml" |
/test-examples="examples/cloudfront/v1beta2/fieldlevelencryptionconfig.yaml" |
/test-examples="examples/backup/v1beta2/plan.yaml" |
/test-examples="examples/autoscaling/v1beta2/attachment.yaml" |
/test-examples="examples/apigateway/v1beta2/stage.yaml" |
/test-examples="examples/accessanalyzer/v1beta2/analyzer.yaml" |
/test-examples="examples/accessanalyzer/v1beta1/analyzer.yaml" |
/test-examples="examples/accessanalyzer/v1beta2/analyzer.yaml" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Description of your changes
For more details, see crossplane/upjet#424
I have:
make reviewable
to ensure this PR is ready for review.Addedbackport release-x.y
labels to auto-backport this PR if necessary.How has this code been tested
See also: crossplane/upjet#424
Uptest runs:
examples/accessanalyzer/v1beta2/analyzer.yaml
Uptest failed with error:conversion webhook for accessanalyzer.aws.upbound.io/v1beta2, Kind=Analyzer failed: Post "https://provider-aws-accessanalyzer.upbound-system.svc:9443/convert?timeout=30s": dial tcp 10.96.172.121:9443: connect: connection refused
Tests in @mergenci's local development environment failed with the same error, but he was able to provision the resource by loading a locally-built provider image to the kind cluster. @turkenf had a similar case in #1334 for
examples/elasticbeanstalk/v1beta2/application.yaml