-
Notifications
You must be signed in to change notification settings - Fork 294
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Can't import CRD if kind is object #1291
Comments
@disaster37 I believe this is happening because there is a built in I am unsure if there is any way around this other than renaming the the resource as you did. |
I haven't understand how it import crd. But I think it can detect that the kind is 'object' and name it with different name. A the end, when it generates yaml resource, it must redo 'object'. Maybee there are a workground to overwrite something on generated with object2 to simply get object when generate kubernetes manifest like overwrite getKind() |
@disaster37 We are going to label this as a p2 issue, which means we will not prioritize implementing a workaround for this issue as it is a pretty rare case. Since there is not way to get around the default Contributions are very much welcome though, so feel free to put up a PR for this issue if you'd like. To get around this issue for now, you can rename the |
I ran into this same issue while trying to import I think a good fix for this would include support for |
This issue has not received any attention in 1 year and will be closed soon. If you want to keep it open, please leave a comment below @mentioning a maintainer. |
Description of the bug:
We can't import CRD with kind
object
.I get error
kubernetes.crossplane.io.ts:91:17 - error TS2339: Property 'entries' does not exist on type 'typeof Object'.
If I rename the ressource
Object2
, it's work.before rename:
after rename:
Reproduction Steps:
Error Log:
Environment:
Other:
This is 🐛 Bug Report
The text was updated successfully, but these errors were encountered: