Is there a plan to release Kotlin Looker SDK jar?

[Lunaticf]

I see this...

Currently Looker does not publish the Kotlin Looker SDK jar so you need to do
the following steps and copy the resultant jar into the `lib` folder of this project. Build
the Kotlin Looker SDK jar as follows

[jkaster]

Yes, we do plan to publish the Kotlin SDK but it hasn't been scheduled for a sprint yet. Sorry but we don't have a timeframe for it yet.

[Lunaticf]

Yes, we do plan to publish the Kotlin SDK but it hasn't been scheduled for a sprint yet. Sorry but we don't have a timeframe for it yet.

Sure, Thanks

[gbotka]

Yes, we do plan to publish the Kotlin SDK but it hasn't been scheduled for a sprint yet. Sorry but we don't have a timeframe for it yet.

@jkaster Do you any update on timeframe?

[kavanpuranik]

Any updates on this? It would be so much easier to consume the SDK if it was published in a Maven artefactory just like every other Java or Kotlin based SDK or open source libraries out there, so I am really surprised that your SDK team didn't prioritize it, especially since its a trivial task.

[daniel-lopes-optimizely]

@jkaster are there any updates on this matter?

[deanlooker]

Based on our priorities and staffing at the moment this is not currently on the near term roadmap, but we will be sure to keep you posted if and when there's any movement.

[daniel-lopes-optimizely]

@deanlooker is there anything we can do to put this on the near term roadmap?

Our team has to build and place the jar into every project we require, and would like to leverage more of Kotlin scripts to easily provision and manage our Looker Model deployment CI/CD workflows. But Kotlin scripts don't communicate with private maven repositories, and having to pass the jar file into every project will be a tech debt nightmare with every new version coming out.

If the other language implementations are being published to their respective central package repos, can we also make publishing consistent for Kotlin? It would reduce our tech debt, speed up our upgrade process, and keep dev experience as frictionless as possible.

[daniel-lopes-optimizely]

In the meantime, anybody that wants to use a dedicated maven repository, they can set their own deployment github actions project and run gradle with a bespoke init script that injects their Org's maven registry into this project, like so:

cat <<- EOF | >> init.gradle.kts
allprojects {
    version = System.getenv("VERSION") ?: "0.0.1"
    apply(plugin = "maven-publish")
    afterEvaluate {
        plugins.withId("maven-publish") {
            configure<PublishingExtension> {
                publications {
                    repositories {
                        maven {
                            name = "GitHubPackages"
                            url = uri("https://maven.pkg.github.com/OWNER/PROJECT_REPOSITORY")
                            credentials {
                                username = System.getenv("USERNAME")
                                password = System.getenv("PASSWORD")
                            }
                        }
                    }
                    create<MavenPublication>("javaPublication") {
                        from(components.getByName("java"))
                    }
                }
            }
        }
    }
}
EOF

./gradlew --init-script init.gradle.kts assemble publish