-
Notifications
You must be signed in to change notification settings - Fork 95
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
[NU-2048] Fix for invalid classloader used for resources in K8sDeploymentManager #7592
base: staging
Are you sure you want to change the base?
Conversation
…k.xml in K8sDeploymentManager
… for defaultMinimalIngress.conf wrong classloader
...server/src/main/scala/pl/touk/nussknacker/ui/process/processingtype/ProcessingTypeData.scala
Outdated
Show resolved
Hide resolved
|
||
// We wrap created DeploymentManagerProvider with this handler to make sure that DM creation logic will use | ||
// correct context classloader | ||
class DeploymentManagerProviderCorrectClassloaderHandler( |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
we can add private [loader]
to hint that it should not be used in other places.
} | ||
} | ||
|
||
override def metaDataInitializer(config: Config): MetaDataInitializer = delegate.metaDataInitializer(config) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
are we sure the other methods don't need the changed context class loader?
I'm not sure, but it seems we cannot exactly predict what the user (who implemented the deployment manager) can do, so wouldn't be safe to change the context class loaded in all these places?
Describe your changes
Checklist before merge