Updates for Kafka cluster and configuration are not/ not always applied

[Patrick-L]

What happened?

Updates for Kafka clusters and Kafka cluster configurations are successfully created in the cluster as CRD, but are not applied in AWS. This means for kafka-cluster they are not changed and for cluster-configurations no new revision is created.

How can we reproduce it?

For Kafka cluster:
Add openMonitoring config to cluster crd. The changes are not visible in the aws management console.

CRD excerpt:

   openMonitoring:
      prometheus:
        jmxExporter:
          enabledInBroker: true
        nodeExporter:
          enabledInBroker: true

For Cluster configuration:
Add new property like "delete.topic.enable=true". The changes are not visible in the aws management console.

CRD excerpt:

    properties:
      - delete.topic.enable=true

What environment did it happen in?

Crossplane version: v0.37.0
Cloud provider: AWS

[hitman99]

We have the same issue. No updates to either Cluster of Configuration gets updated. It seems that only Create and Update hooks were implemented for these resources and it's using nopUpdate for updates.

[github-actions]

Crossplane does not currently have enough maintainers to address every issue and pull request. This issue has been automatically marked as stale because it has had no activity in the last 90 days. It will be closed in 14 days if no further activity occurs. Leaving a comment starting with /fresh will mark this issue as not stale.