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
Remove extension mock modules #3924
Comments
@shawkins Do we need to remove the |
@anurag-rajawat they should not be removed yet. To ease the migration to 6.0 they will still initially be present but deprecated. In a subsequent release they will be removed. |
@anurag-rajawat or any other community user interested in picking up an issue, we are ready for this. It is mostly removing the modules, but it will also require cleaning up any tests and examples that still reference them. |
@shawkins I would love to work on this, assign this to me. |
Signed-off-by: Anurag Rajawat <anuragsinghrajawat22@gmail.com>
Signed-off-by: Anurag Rajawat <anuragsinghrajawat22@gmail.com>
Signed-off-by: Anurag Rajawat <anuragsinghrajawat22@gmail.com>
Signed-off-by: Marc Nuri <marc@marcnuri.com>
* since kubernetes client 6.2.0, no more need of a specific mock dependency fabric8io/kubernetes-client#3924
It is impacting mostly the Traits completion/validation * Embed the Camel K CRDs for now. For next iteration, it would nice to: use one from Camel K CRD jar (or another upstream artifact) and then also allow possibility to load from the cluster * Requires to use Jackson Dataformat loader as Snake Yaml one is less permissive and throwing errors * since kubernetes client 6.2.0, no more need of a specific mock dependency fabric8io/kubernetes-client#3924 * No more providing default values as they not yet in CRD apache/camel-k#4726 * Some description are now a lot less precise, adapted tests and reported apache/camel-k#4727 Signed-off-by: Aurélien Pupier <apupier@redhat.com>
It is impacting mostly the Traits completion/validation * Embed the Camel K CRDs for now. For next iteration, it would nice to: use one from Camel K CRD jar (or another upstream artifact) and then also allow possibility to load from the cluster * Requires to use Jackson Dataformat loader as Snake Yaml one is less permissive and throwing errors * since kubernetes client 6.2.0, no more need of a specific mock dependency fabric8io/kubernetes-client#3924 * No more providing default values as they not yet in CRD apache/camel-k#4726 * Some description are now a lot less precise, adapted tests and reported apache/camel-k#4727 Signed-off-by: Aurélien Pupier <apupier@redhat.com>
It is impacting mostly the Traits completion/validation * Embed the Camel K CRDs for now. For next iteration, it would nice to: use one from Camel K CRD jar (or another upstream artifact) and then also allow possibility to load from the cluster * Requires to use Jackson Dataformat loader as Snake Yaml one is less permissive and throwing errors * since kubernetes client 6.2.0, no more need of a specific mock dependency fabric8io/kubernetes-client#3924 * No more providing default values as they not yet in CRD apache/camel-k#4726 * Some description are now a lot less precise, adapted tests and reported apache/camel-k#4727 Signed-off-by: Aurélien Pupier <apupier@redhat.com>
It is impacting mostly the Traits completion/validation * Embed the Camel K CRDs for now. For next iteration, it would nice to: use one from Camel K CRD jar (or another upstream artifact) and then also allow possibility to load from the cluster * Requires to use Jackson Dataformat loader as Snake Yaml one is less permissive and throwing errors * since kubernetes client 6.2.0, no more need of a specific mock dependency fabric8io/kubernetes-client#3924 * No more providing default values as they not yet in CRD apache/camel-k#4726 * Some description are now a lot less precise, adapted tests and reported apache/camel-k#4727 Signed-off-by: Aurélien Pupier <apupier@redhat.com>
It is impacting mostly the Traits completion/validation * Embed the Camel K CRDs for now. For next iteration, it would nice to: use one from Camel K CRD jar (or another upstream artifact) and then also allow possibility to load from the cluster * Requires to use Jackson Dataformat loader as Snake Yaml one is less permissive and throwing errors * since kubernetes client 6.2.0, no more need of a specific mock dependency fabric8io/kubernetes-client#3924 * No more providing default values as they not yet in CRD apache/camel-k#4726 * Some description are now a lot less precise, adapted tests and reported apache/camel-k#4727 Signed-off-by: Aurélien Pupier <apupier@redhat.com>
It is impacting mostly the Traits completion/validation * Embed the Camel K CRDs for now. For next iteration, it would nice to: use one from Camel K CRD jar (or another upstream artifact) and then also allow possibility to load from the cluster * Requires to use Jackson Dataformat loader as Snake Yaml one is less permissive and throwing errors * since kubernetes client 6.2.0, no more need of a specific mock dependency fabric8io/kubernetes-client#3924 * No more providing default values as they not yet in CRD apache/camel-k#4726 * Some description are now a lot less precise, adapted tests and reported apache/camel-k#4727 Signed-off-by: Aurélien Pupier <apupier@redhat.com>
Is your task related to a problem? Please describe
After #3912 the extension mock modules are no longer needed.
Describe the solution you'd like
The user facing classes will have been deprecated, so this issue is a reminder to remove them at a later time - 6.1?
Additional context
The usage of these modules are no longer required since the generic Kubernetes Mock Server can be used instead (is preferred).
kubernetes-client/doc/MIGRATION-v6.md
Line 238 in 43af167
The text was updated successfully, but these errors were encountered: