set the channel description: This space is for any and all conversations related to using Pulumi with Java.

Hey have anyone figured out how to use pulumi with java and gradle with a multi module setup?

Howdy java folks👋

Any idea when Output-Based functions might be available in Java? I'm trying to use AzureAd getGroup. Just to make sure I understand, I cannot do this until it is supported?

Hello, So excited for Java release. I am trying to use Input Bucket Resource properties (currently publicAccessBlockConfiguration, later on loggingConfiguration etc)… but am not able to move ahead. Are Input available in Java? Any code snipplets around these would be super helpful. Thanks!

Can any other JVM based language (e.g. groovy, Jruby, Kotlin or Scala) be used with Pulumi?

👋 hi all, I’m excited about the Java support. I just wanna check, is the team aware that the SDK API Javadocs subsite is returning a 404? I mean https://www.pulumi.com/registry/packages/java/api-docs/ Which is linked from https://www.pulumi.com/docs/reference/pulumi-sdk/

Where is the equivalent to

pulumi/getStack()

from the JS/TS SDK?

Are there javadocs for the aws provider published anywhere?

I was trying to learn kotlin and typesafe builders for kotlin and how we might use them for idiomatic kotlin resource construction

managedCluster("cluster-1") {
    args {
        identity {
            type = ResourceIdentityType.SystemAssigned
        }
        servicePrincipalProfile {
            clientId = "msi"
        }
        agentPoolProfiles {
            name   = "pool1"
            count  = 1
            osType = OSType.Linux
            osSKU  = OSSKU.Ubuntu
            vmSize = "standard_a2_v2"
            mode   = AgentPoolMode.System
        }
    }
    opts {
        protect = true
    }
}

It looks like I'm just writing terraform. I'll probably have to modify this to support supplying both

T

and

Output<T>

just thought I'd share.

I was thinking how difficult it would be to just generate a wrapper/translator from typesafe Kotlin builders to Java builders generated in the providers.

so a codegen to wrap what the other codegen generates ;D

Is it possible to implement a “dynamic provider” with the Java SDK, at this point?

I'm working on adding stack transformations to the Java SDK API and I need your collective help. Please share your thoughts :) This is the feature: https://www.pulumi.com/docs/intro/concepts/resources/options/transformations/#stack-transformations An this is the issue with two proposed APIs: https://github.com/pulumi/pulumi-java/issues/478#issuecomment-1144098656

📓 https://github.com/pulumi/pulumi-java/blob/main/CHANGELOG.md#030-2022-06-01 is semi-out - you can get it via GitHub releases or Maven Central (SDK) but it will only be installed by default with Pulumi CLI starting next week. Release was delayed this week. Fav feature JBang support contributed by maxandersen. Thank you!

👋 Hallo Team!

I'am testing an idea and wanted to use prebuild jar with

runtime.options.binary

. But unfortunatly it seems to be executed with a wrong java version-setting. All my projects are compiled to java11 and the output says, that pulumi starts up the right java runtime:

EVERE: Running program [PID: 25370](/usr/lib/jvm/java-11-openjdk-amd64/bin/java -jar target/pulumytemplate-1.0-SNAPSHOT-jar-with-dependencies.jar) failed with an unhandled exception:

But it fails with java.util.concurrent.CompletionException: java.lang.Error: Unresolved compilation problems: References to interface static methods are allowed only at source level 1.8 or above Lambda expressions are allowed only at source level 1.8 or above Lambda expressions are allowed only at source level 1.8 or above at java.base/java.util.concurrent.CompletableFuture.encodeThrowable(CompletableFuture.java:314) at java.base/java.util.concurrent.CompletableFuture.completeThrowable(CompletableFuture.java:319) at java.base/java.util.concurrent.CompletableFuture$AsyncSupply.run(CompletableFuture.java:1702) at java.base/java.util.concurrent.CompletableFuture$AsyncSupply.exec(CompletableFuture.java:1692) at java.base/java.util.concurrent.ForkJoinTask.doExec(ForkJoinTask.java:290) at java.base/java.util.concurrent.ForkJoinPool$WorkQueue.topLevelExec(ForkJoinPool.java:1020) at java.base/java.util.concurrent.ForkJoinPool.scan(ForkJoinPool.java:1656) at java.base/java.util.concurrent.ForkJoinPool.runWorker(ForkJoinPool.java:1594) at java.base/java.util.concurrent.ForkJoinWorkerThread.run(ForkJoinWorkerThread.java:183) Caused by: java.lang.Error: Unresolved compilation problems: References to interface static methods are allowed only at source level 1.8 or above Lambda expressions are allowed only at source level 1.8 or above Lambda expressions are allowed only at source level 1.8 or above at inc.pulumi.firsttry.ExternalPulumi.getStorageAccountPrimaryKey(ExternalPulumi.java:86) at inc.pulumi.firsttry.ExternalPulumi.callMe(ExternalPulumi.java:76) at myproject.App.lambda$0(App.java:36) at com.pulumi.internal.PulumiInternal.lambda$runAsync$1(PulumiInternal.java:62) at java.base/java.util.concurrent.CompletableFuture$AsyncSupply.run(CompletableFuture.java:1700) ... 6 more Any ideas?

@brave-dawn-64711 do you happen to know what could be going on?

unfortunately I haven't seen an error like that, not sure what happened, sorry

is it possible that somehow wrong javac is used?

I am sorry. Showhow the inner-jar was somehow build with another version.

Hello Pulumi team. I got a simple question related to the newly available Java SDK. Are there any written guides or material on how to use the SDK with other JVM based languages? For a bit of context, I have plenty of experience working with Terraform, but we are seriously considering switching to Pulumi because we are unifying our technologies around Clojure and its ecosystem. Additionally, I came to know Pulumi now supports a Java SDK, but haven't found an official guide on how to use it in a non-Java project. Lastly, bear with my lack of knowledge, since I have no experience using Pulumi yet, so I might miss some basic concepts. From a Clojure perspective, we would be in charge of compiling and bundling the JAR packages, so we only need Pulumi to take the JAR and run it I suppose. I don't know if there are any other considerations. Thanks for your support!

Hi @aloof-dawn-47658, using Clojure with Pulumi sounds exciting! I'm not aware of any official guides on how to approach using Java SDK with other JVM languages, but my understanding is as follows: • general guidelines of using Java APIs from your language should apply • best integration of Pulumi CLI and JVM-centric build systems will be for maven and gradle, at the moment • some APIs might not "look native" since they are limited by Java features

it is possible to just run a jar directly, please refer to the "binary" option described here: https://www.pulumi.com/docs/reference/pulumi-yaml/

and here is an example of usage https://github.com/pulumi/pulumi-java/blob/main/tests/examples/minimal/Pulumi.yaml#L6 example uses maven, but the "binary" option is build tool agnostic, it just needs the default main of the jar to be pulumi main program

your experience with terraform is transferrable to pulumi, state management and basic operations are very similar

please read more about similarities and interoperability with terraform here: https://www.pulumi.com/docs/guides/adopting/from_terraform/ there's even a converter (not perfect but a good start): https://www.pulumi.com/tf2pulumi/