Checklist

• I did not find a related open issue.
• I did not find a solution in the troubleshooting guide: (https://cloud.google.com/config-connector/docs/troubleshooting)
• If this issue is time-sensitive, I have submitted a corresponding issue with GCP support.

Bug Description

spec.resourceId isn't respected when provided, metadata.name is set.

Additional Diagnostic Information

This is on version 1.49.1 deployed manually onto GKE

Kubernetes Cluster Version

Server Version: v1.18.16-gke.2100

Config Connector Version

1.49.1

Config Connector Mode

cluster

Log Output

Steps to Reproduce

Steps to reproduce the issue

• create resource with spec.resourceId and metadata.name that are different
• schedule it, you'll get underlying resource not exists error etc
• if you then move the same spec.resourceId to metadata.name, it'll create immediately, implying that the spec.resourceId was a valid identifier from the start