Add conversion functions for handling some breaking API changes#1118
Conversation
cb1a28d to
14598be
Compare
c8c5505 to
3d9a041
Compare
Signed-off-by: Sergen Yalçın <yalcinsergen97@gmail.com>
…rsion Signed-off-by: Sergen Yalçın <yalcinsergen97@gmail.com>
Signed-off-by: Sergen Yalçın <yalcinsergen97@gmail.com>
Signed-off-by: Sergen Yalçın <yalcinsergen97@gmail.com>
Signed-off-by: Sergen Yalçın <yalcinsergen97@gmail.com>
Signed-off-by: Sergen Yalçın <yalcinsergen97@gmail.com>
Signed-off-by: Sergen Yalçın <yalcinsergen97@gmail.com>
Signed-off-by: Sergen Yalçın <yalcinsergen97@gmail.com>
Signed-off-by: Sergen Yalçın <yalcinsergen97@gmail.com>
Signed-off-by: Sergen Yalçın <yalcinsergen97@gmail.com>
0454a67 to
2afd235
Compare
|
/test-examples="examples/elasticache/v1beta1/replicationgroup-engineVersion.yaml" |
|
/test-examples="examples/autoscaling/v1beta1/attachment.yaml" |
|
/test-examples="examples/connect/v1beta1/routingprofile.yaml" |
|
/test-examples="examples/ec2/v1beta1/route.yaml" |
ulucinar
left a comment
There was a problem hiding this comment.
Thanks @sergenyalcin, lgtm.
|
The https://github.com/upbound/provider-aws/actions/runs/7745386352 job's import failed because of a known issue about the testing logic. The similar issue is here: #978 There is not any real issue in the resource lifecycle. This appears only import step of some resources. |
|
@sergenyalcin is this snippet from the uptest logs in https://github.com/upbound/provider-aws/actions/runs/7745386352 a concern? |
|
Also, if we can get a new release of uptest, we'll be able to skip the import step per-resource with an annotation. |
|
Hi @mbbush, |
Description of your changes
This PR adds,
aws_autoscaling_attachmentaws_autoscaling_groupaws_connect_hours_of_operationaws_connect_queueaws_connect_routing_profileaws_db_instanceaws_elasticache_replication_groupaws_msk_clusteraws_routeaws_route_tableaws_autoscaling_groupaws_connect_routing_profileaws_elasticache_replication_groupaws_msk_clusterI have:
make reviewable testto ensure this PR is ready for review.How has this code been tested
For the following resources the spec.forProvider and status.atProvider was tested. While testing, checked two versions of resources.
aws_autoscaling_attachmentaws_autoscaling_groupaws_connect_hours_of_operationaws_connect_queueaws_connect_routing_profileaws_elasticache_replication_groupaws_msk_clusteraws_route_table