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
{{ message }}
This repository has been archived by the owner on Dec 15, 2022. It is now read-only.
The problem is that project is not a valid field for metal_device. The field is project_id.
I received no error messages about this typo. make generate succeeded.
When I eventually discovered the typo and set the field name in the map to project_id, an additional file (apis/device/v1alpha1/zz_generated.resolvers.go) was generated.
That's due to the look-up mechanism we have for this feature where for each field we check whether there is a referencer field, hence no error if nothing hits the given reference entry. One option could be to validate the whole configuration object before starting any operation.
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.
What happened?
While working on an Equinix Metal Terrajet provider, I created a
metal_device
project
field reference, associated with themetal_project
identifier.The problem is that
project
is not a valid field formetal_device
. The field isproject_id
.I received no error messages about this typo.
make generate
succeeded.When I eventually discovered the typo and set the field name in the map to
project_id
, an additional file (apis/device/v1alpha1/zz_generated.resolvers.go
) was generated.How can we reproduce it?
crossplane-contrib/provider-tf-equinix-metal@81a6d89
The text was updated successfully, but these errors were encountered: