-
Notifications
You must be signed in to change notification settings - Fork 133
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
Bump Terraform provider version to v4.66.0 #697
Bump Terraform provider version to v4.66.0 #697
Conversation
/test-examples="examples/appautoscaling/policy.yaml" |
/test-examples="examples/appmesh/route.yaml" |
/test-examples="examples/appmesh/virtualrouter.yaml" |
/test-examples="examples/cognitoidp/user.yaml" |
/test-examples="examples/scheduler/schedule.yaml" |
/test-examples="examples/secretsmanager/secretrotation.yaml" |
76cfe6d
to
c47be04
Compare
/test-examples="examples/securityhub/account.yaml" |
1 similar comment
/test-examples="examples/securityhub/account.yaml" |
c47be04
to
c9f55cc
Compare
/test-examples="examples/securityhub/account.yaml" |
1 similar comment
/test-examples="examples/securityhub/account.yaml" |
5de8e22
to
ff806fe
Compare
This PR is ready for review. |
- aws_autoscaling_policy - aws_securityhub_account - aws_secretsmanager_secret_rotation - aws_ssoadmin_permission_set_inline_policy
ff806fe
to
971f83a
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.
Thanks @turkenf LGTM!
Description of your changes
Bumps Terraform provider version to
v4.66.0
.Fixes: #684
I have:
make reviewable test
to ensure this PR is ready for review.How has this code been tested
Breaking CRD schema changes
appautoscaling.aws.upbound.io_policies.yaml
, Manuallyappmesh.aws.upbound.io_routes.yaml
, Uptestappmesh.Route
=> https://github.com/upbound/provider-aws/actions/runs/4919030429appmesh.VirtualNode
=> https://github.com/upbound/provider-aws/actions/runs/4919030429appmesh.Mesh
=> https://github.com/upbound/provider-aws/actions/runs/4919030429appmesh.VirtualRouter
=> https://github.com/upbound/provider-aws/actions/runs/4919030429appmesh.aws.upbound.io_virtualrouters.yaml
, Uptestappmesh.VirtualNode
=> https://github.com/upbound/provider-aws/actions/runs/4919045845appmesh.Mesh
=> https://github.com/upbound/provider-aws/actions/runs/4919045845autoscaling.aws.upbound.io_policies.yaml
, Manuallycognitoidp.aws.upbound.io_userpools.yaml
, Uptestcognitoidp.User
=> https://github.com/upbound/provider-aws/actions/runs/4919093954cognitoidp.UserPool
=> https://github.com/upbound/provider-aws/actions/runs/4919093954elasticache.aws.upbound.io_usergroups.yaml
, Manuallyelasticache.aws.upbound.io_users.yaml
I could not create
elasticache.User
resource because sensitive input arrays are not transferred to Terraform and I created an issue in upjet for this: crossplane/upjet#202Also, there is a pre-opened issue in the provider-aws repo regarding this: #151
medialive.aws.upbound.io_channels.yaml
, Manuallyscheduler.aws.upbound.io_schedules.yaml
, Uptestscheduler.Schedule
=> https://github.com/upbound/provider-aws/actions/runs/4919142257sqs.Queue
=> https://github.com/upbound/provider-aws/actions/runs/4919142257iam.Role
=> https://github.com/upbound/provider-aws/actions/runs/4919142257secretsmanager.aws.upbound.io_secretrotations.yaml
, Manuallyssoadmin.aws.upbound.io_permissionsetinlinepolicies.yaml
, ManuallyNative state schema version changes
aws_securityhub_account
, Uptestsecurityhub.Account
=> https://github.com/upbound/provider-aws/actions/runs/4934998808