[Bug]: fields in Init provider are not ignored

[MichaelHarden]

Is there an existing issue for this?

• [X] I have searched the existing issues

Affected Resource(s)

• dynamodb.aws.upbound.io/v1beta1

Resource MRs required to reproduce the bug

apiVersion: dynamodb.aws.upbound.io/v1beta1 kind: Table metadata: name: test-initprovider spec: forProvider: attribute:

• name: Artist type: S billingMode: PROVISIONED deletionProtectionEnabled: false hashKey: Artist region: us-west-2 initProvider: readCapacity: 1 writeCapacity: 1

Steps to Reproduce

1. Apply the MR.
2. In AWS change read or write capacity to something else.
3. Observe Crossplane will re-sync and reset read and write capacity back to 1

What happened?

Since read and write capacity was set in the InitProvider and not ForProvider i would expect Crossplane to ignore future changes to these parameters. But, when changes are made to the read and write capacity, apart from the Crossplane MR, Crossplane continuously resets the values back.

Relevant Error Output Snippet

No response

Crossplane Version

v1.15.0

Provider Version

v1.3.1

Kubernetes Version

v1.28, v1.21

Kubernetes Distribution

K3D and EKS

Additional Info

No response

[nsilve]

I have faced the same issue with another resource. I believe that documentation is not very clear, but you can overcome this issue by removing the LateInitialize management policy.

[MichaelHarden]

Eventually figured this out. The way around this is to change the management policy on the MR to:

managementPolicies: 
            - "Create"
            - "Update"
            - "Delete"
            - "Observe"

This allows for initProvider to not update the forProvider while also maintaining the forProvider's drift protection.