Closed musketyr closed 5 years ago
There is a common idiom to use aws.accountId during the configuration phase of the deployment task:
aws.accountId
task deploy(type: jp.classmethod.aws.gradle.lambda.AWSLambdaMigrateFunctionTask, dependsOn: shadowJar) { functionName = "@project.name@" handler = "@defaultPackage@.@project.className@Function::@project.propertyName@" role = "arn:aws:iam::${aws.accountId}:role/lambda_basic_execution" runtime = com.amazonaws.services.lambda.model.Runtime.Java8 zipFile = shadowJar.archivePath memorySize = 256 timeout = 60 }
For the current version, the build fails in the configuration phase if aws.accountId cannot be evaluated because of lack of credentials.
you're welcome! any plans for release soon?
There is a common idiom to use
aws.accountId
during the configuration phase of the deployment task:For the current version, the build fails in the configuration phase if
aws.accountId
cannot be evaluated because of lack of credentials.