-
Story
-
Resolution: Done
-
Normal
-
None
-
None
-
None
If you try to run applyconfiguration-gen on MachineConfigControllerStatus, the embedded (non-pointer) ObjectReference seems to confuse it, and it generates code that doesn't work quite right:
# github.com/openshift/client-go/machineconfiguration/applyconfigurations/machineconfiguration/v1 vendor/github.com/openshift/client-go/machineconfiguration/applyconfigurations/machineconfiguration/v1/machineconfigpoolstatusconfiguration.go:27:11: cannot use &value (value of type *string) as type string in assignment vendor/github.com/openshift/client-go/machineconfiguration/applyconfigurations/machineconfiguration/v1/machineconfigpoolstatusconfiguration.go:35:16: cannot use &value (value of type *string) as type string in assignment vendor/github.com/openshift/client-go/machineconfiguration/applyconfigurations/machineconfiguration/v1/machineconfigpoolstatusconfiguration.go:43:11: cannot use &value (value of type *string) as type string in assignment vendor/github.com/openshift/client-go/machineconfiguration/applyconfigurations/machineconfiguration/v1/machineconfigpoolstatusconfiguration.go:51:10: cannot use &value (value of type *types.UID) as type types.UID in assignment vendor/github.com/openshift/client-go/machineconfiguration/applyconfigurations/machineconfiguration/v1/machineconfigpoolstatusconfiguration.go:59:17: cannot use &value (value of type *string) as type string in assignment vendor/github.com/openshift/client-go/machineconfiguration/applyconfigurations/machineconfiguration/v1/machineconfigpoolstatusconfiguration.go:67:22: cannot use &value (value of type *string) as type string in assignment vendor/github.com/openshift/client-go/machineconfiguration/applyconfigurations/machineconfiguration/v1/machineconfigpoolstatusconfiguration.go:75:16: cannot use &value (value of type *string) as type string in assignment make: *** [Makefile:40: _build-machine-config-daemon] Error 2
It looks like it's the only place in our types we have an embedded non-pointer object like that?
The rest of the generators seem to be okay with it, so I'm assuming it's not just a "this is terrible practice, don't ever embed an object like that".
Might be able to change it to a pointer but I haven't tried that yet.
I think it's in here somewhere:
- is related to
-
MCO-726 API Migration Cleanup: Remove client-go ObjectReference hack by the end of 4.15
-
- Closed
-