Convert jib.to.auth.username and jib.to.auth.password to properties

[dubinsky]

I think it makes sense to convert jib.to.auth.username and jib.to.auth.password from Strings to Property<String>s in AuthParameters, just as it was done in #2727 / #2739 for jib.to.image in TargetImageParameters.

Motivation is the same as withjib.to.image: make JIB configuration lazier, allowing setting the values (for instance) from other plugins. In my case, I'd like to be able to set the authentication parameters to the values exposed by a Cloud Run plugin and avoid duplicating the code that retrieves them.

Thanks!

[chanseokoh]

Hi @dubinsky,

That makes a lot of sense. Looks like you already looked into a way to fix this. Our resources are very constrained, but if you put up a PR, we will review it. Thanks!

[dubinsky]

if you put up a PR, we will review it. Thanks!

Thank you, @chanseokoh, it's an honor!
#2906

[chanseokoh]

@dubinsky Jib 2.7.0 has been released with this feature!

[dubinsky]

@dubinsky Jib 2.7.0 has been released with this feature!

Thank you so much!!!

[bric3]

Hi I had a build like this :

jib {
    // ...
    to {
        def gcpProject = System.getenv('REGISTRY_TARGET') ?: 'dev-sandbox'
        image = "eu.gcr.io/${gcpProject}/${project.name}"
        auth {
            username = 'oauth2accesstoken'
            password = System.getenv('GCR_TOKEN') ?: ''
        }
        tags = [appVersion]
    }
}

But now this fails in dev because I don't have the GCR_TOKEN environment variable locally, only the CI has it.

Build file 'path/to/build.gradle' line: 41

A problem occurred evaluating project ':the-project'.
> Cannot set the value of a property using a null provider.

Right now the only workaround I found is this : System.getenv('GCR_TOKEN') ?: '', but is there something more straightforward ?

[chanseokoh]

@bric3 perhaps for your dev machine, remove the auth { ... } and configure gcloud credential helper? Basically running gcloud auth configure-docker after gcloud auth login.

FYI, since the username on CI is oauth2accesstoken, looks like your CI is using the access token method. In this case, the content of GCR_TOKEN would be the output of gcloud auth print-access-token as documented there. (It's a short-lived token expiring after an hour.)

---

For the general ways to configure auth in Jib, see this FAQ.