Skip to content
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

KnativeResourceMappingsProvider uses wrong apiGroup #1838

Closed
iocanel opened this issue Oct 29, 2019 · 2 comments
Closed

KnativeResourceMappingsProvider uses wrong apiGroup #1838

iocanel opened this issue Oct 29, 2019 · 2 comments

Comments

@iocanel
Copy link
Member

iocanel commented Oct 29, 2019

Uses knative.dev while it should be using serving.knative.dev etc.

iocanel added a commit to iocanel/kubernetes-client that referenced this issue Oct 29, 2019
… missing

entries for messaging and eventing.
iocanel added a commit to iocanel/kubernetes-client that referenced this issue Oct 30, 2019
… missing

entries for messaging and eventing.
@stale
Copy link

stale bot commented Jan 27, 2020

This issue has been automatically marked as stale because it has not had any activity since 90 days. It will be closed if no further activity occurs within 7 days. Thank you for your contributions!

@shawkins
Copy link
Contributor

Resolving as out-of-date as this has already been addressed. This sort of thing won't happen if we move forward with the jandex discovery, or if we just refactor the mapping provider to be based only on class - which is also part of #4024

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants