-
Notifications
You must be signed in to change notification settings - Fork 21
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
Serialization error when using helm to install a chart with Java #629
Comments
@t0yv0 do you want to keep this on the triage queue until you get to it? |
Ah sorry about that, I just want to get it on @pawelprazak radar. I logged the issue from Community Slack. This does need fixing when possible so I can remove the label. |
This is the cause for the error, the annotation for exports does not support nested generic types, so List is raw/untyped.
The easiest solution would be to relax the converter validation, but I'm not sure about the second order consequences. I don't expect that overcoming java annotations limits would be easy or readable, as discussed here https://stackoverflow.com/a/35776898/539481 |
Since breaking changes to providers are becoming quite painful now, we should try to avoid that (e.g. make SDK work with "old codegen + new codegen") here. Thank you! |
I am still experiencing this problem. Here is a complete stack definitition: import com.pulumi.Context
import com.pulumi.Pulumi
import com.pulumi.kubernetes.helm.v3.Release
import com.pulumi.kubernetes.helm.v3.ReleaseArgs
import com.pulumi.kubernetes.helm.v3.inputs.RepositoryOptsArgs
import com.pulumi.resources.CustomResourceOptions
object App {
@JvmStatic
fun main(args: Array<String>) {
Pulumi.run { pulumiContext: Context ->
Release("nginx",
ReleaseArgs.builder()
.chart("nginx-ingress")
.version("1.24.4")
.repositoryOpts(RepositoryOptsArgs.builder().repo("https://charts.helm.sh/stable").build())
.build(),
CustomResourceOptions.builder()
.build());
}
}
}
Using pulumi 3.43.1 with pulumi-java 0.6.0. This issue should get reopened. |
@hnicke I'm speculating here, but there is a possibility that an old kubernetes provider is used and this may re-surface the problem. It is possible to remove all kubernetes provider versions from local cache using this command:
Afterwards, a new version would be downloaded automatically when doing |
Btw, in the Output of
I removed the cached kubernetes plugins:
I've removed all the other plugins from the cache as well. During execution of the next
However, I'm still experiencing the same error ( Output of
|
Thank you for trying and for detailed response, it was worth a try ;) It's unfortunate that the problem persists, we'll need to take a closer look. |
Unfortunately I run into the same problem trying to deploy a helm chart to GKE with java (using Kotlin). As in the pulumi helm package for java only the com.pulumi.kubernetes.helm.v3.Release class is available, I cannot test other strategies. Following my stacktrace, implementation and versions. Please tell me if I do something wrong here, as I need to deploy several different helm charts.
Failing implementation:
Pulumi Java 0.6.0 |
We are experiencing this problem using kotlin as well, when:
|
Update: |
I can confirm that this issue still exists with pulumi-java 0.6.0. Even tried the latest kubernetes alpha plugin and it didn't make a difference. |
Can confirm that unfortunately the issue still persists with all pulumi dependencies being up-to-date. |
As of now, all helm chart installations are working fine for me! 🥳 |
What happened?
Error when using helm to install a chart with Java.
Steps to reproduce
Expected Behavior
Working code.
Actual Behavior
Versions used
No response
Additional context
No response
Contributing
Vote on this issue by adding a 👍 reaction.
To contribute a fix for this issue, leave a comment (and link to your pull request, if you've opened one already).
The text was updated successfully, but these errors were encountered: