You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Only include DBSubnetGroupName inside ModifyDBInstanceRequest when there is delta (#61)
Issue #, if available: aws-controllers-k8s/community#1147
Description of changes:
* By default, ACK code-generator creates `UpdateRequest` payload completely from desired state of the resource and does not consider `delta` between `desired` & `latest` while creating the UpdateRequest payload.
* Due to above the UpdateRequest also contains the fields which are same between desired and latest state.
* This works fine in most cases where AWS Update APIs ignore the no-op updates in the backend but RDS's `ModifyDBInstance` API does not. If ModifyDBInstance API tries to update `DBSubnetGroupName` with the same name, it returns an error "InvalidVPCNetworkStateFault: The specified DB instance is already in the target DB subnet group.\n\tstatus code: 400"
* I have added a hook that checks for the delta of `DBSubnetGroupName` before making the ModifyDBInstance API call
-----
* Tested manually and validated that the "InvalidVPCNetworkStateFault" error goes away
* added e2e test as well covering above case
By submitting this pull request, I confirm that my contribution is made under
the terms of the Apache 2.0 license.
0 commit comments