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
feat(ack): bump ack & aws-go-sdk-v1 to 1.42.0 #1122
feat(ack): bump ack & aws-go-sdk-v1 to 1.42.0 #1122
Conversation
@muvaf anything i need to check more ? i will start testing the resources and will give feedback here |
@haarchri can we save this to after the release on Feb 9th? |
@muvaf we can do this for 0.25 release |
3ab4638
to
a6b344a
Compare
@muvaf how do you feel about getting this in now that v0.24 has shipped? 😊 🤔 |
I will do today a check if our examples will work think then we can go |
2d17d9f
to
6ee453c
Compare
added current state of testing |
added next testing and updated examples for docdb, cloudfront, mq, rds |
Signed-off-by: Yury Tsarev <yury@upbound.io>
Signed-off-by: Yury Tsarev <yury@upbound.io>
First of all, great work @haarchri ! I can answer my own question.. provider-aws needs to follow the same version as the code-generator-project is using. |
@goober yes because of the code-generator version ;) |
85f5613
to
deba226
Compare
b155986
to
01c4352
Compare
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.
Thank you for taking care of this @haarchri ! I tried to sweep through the CRDs for breaking changes but there might be some that I couldn't catch. I think that's the most important part when we do an SDK bump along with the tests that you've done.
01c4352
to
a91e30c
Compare
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.
A few small nitpick comments but looking great. Thanks @haarchri !
Signed-off-by: haarchri <chhaar30@googlemail.com>
a19e007
to
5098e0d
Compare
Signed-off-by: haarchri <chhaar30@googlemail.com>
e2e-tests are failing since we merged crossplane/crossplane#2932
tested locally with crossplane 1.6.3 without issues |
Signed-off-by: haarchri <chhaar30@googlemail.com>
we changed e2e tests using crossplane stable channel as of crossplane/crossplane#2944 |
Signed-off-by: Yury Tsarev <yury@upbound.io>
Remove the Terraform CLI from the provider package and deprecate the relevant provider command-line flags
Signed-off-by: haarchri chhaar30@googlemail.com
Description of your changes
generator-config.yaml
ec2 vpcendpoints clientToken
(Create&CreateOutput) fields and added preCreatekafka server
ZookeeperConnectString
andZookeeperConnectStringTLS
because these fields should only available via connectionSecret not as input fieldsmq broker
publiclyAccessible
andautoMinorVersionUpgrade
docdb
to fits Ref/Selectorcloudfront distribution
originAccessIDentity
tooriginAccessIdentity
rds
to fits same region then our other examplesrds instance
fixing the constant configuring-enhanced-monitoring state changesec2 vpcpeeringconnection
vpcPeerIDRef/Selectorsecretsmanager secret
to have stringSecretRef for testingapigatewayv2 vpc-link
in v1beta1ec2 launchtemplateversion
failed to describe LaunchTemplateVersion: InvalidLaunchTemplateName.NotFoundException: The specified launch template, with template name test-crossplane-obj, does not exist.
changed required fields:
tested with master and this PR - the migration is save
Fixes #853
Fixes #918
Fixes #980
I have:
make reviewable test
to ensure this PR is ready for review.How has this code been tested
Done
efs, kms, athena, glue, neptune, transfer, lambda, mq, kinesis, cloudfront, iot, docdb, rds, sfn, cloudwatchlogs, elbv2, dynamodb, ec2, route53resolver, servicediscovery, elasticache, secretsmanager, apigatewayv2, eks, ram
and deleted all resources afterwards