I can see from documentation that if it’s possible to use the builtin credential providers Declaring repositories then gradle can avoid retrieving the credentials needed unless it is necessary.
It’s possible to get to a point where I can use a system property to store the token generated and pull it back out so that for a given run, even with multiple projects only one token is generated to keep down the latency. It would be annoying though on slower connections and most of the time after the first run it should be unnecessary unless there is a need to refresh dependencies.
Is there any way to do this when dealing with custom authentication handling? I don’t think that the existing authentication APIs support CodeArtifact, but it appears that it’s also not possible to define the repositories block in a way that skips executing the block unless the credentials are needed. Or at least not obvious.
Unless I got you wrong, why can’t you use credentials(PasswordCredentials::class)?
As it pulls the credentials from project properties, you can supply them as environment variable, or as system property, or as commandline argument, or as content of a properties file.
I’ve been trying to experiment a bit in that area but I keep bumping into where the code says the credentials type is unknown and lists only 3 that are supported.
Unknown credentials type: ‘GenerateCodeArtifactPasswordCredentials’ (supported types: org.gradle.api.artifacts.repositories.PasswordCredentials, org.gradle.api.credentials.AwsCredentials and org.gradle.api.credentials.HttpHeaderCredentials).
Looking around I’m seeing the following checks and I’m wondering if I’m just out of luck here? Essentially gradle requires that the Credentials is one of the build in and otherwise can only supply the values but not provide a custom class to resolve?