Closed trisberg closed 5 years ago
To reproduce:
export GCP_PROJECT=$(gcloud config get-value core/project)
export GIT_REPO=https://github.com/trisberg/upper.git
riff function create java upper --git-repo $GIT_REPO --image gcr.io/$GCP_PROJECT/upper --verbose
It works fine doing a local build with pack. I get:
-----> riff Buildpack 1.0.0-BUILD-SNAPSHOT
-----> riff Java Invoker 0.1.2: Reusing cached launch layer
-----> Process types:
web: java -jar /workspace/io.projectriff.riff/riff-invoker-java/java-function-invoker-0.1.2-exec.jar $JAVA_OPTS --function.uri='file:///workspace/app?handler=uppercase'
function: java -jar /workspace/io.projectriff.riff/riff-invoker-java/java-function-invoker-0.1.2-exec.jar $JAVA_OPTS --function.uri='file:///workspace/app?handler=uppercase'
This is caused because the write-riff-toml
stage is overwriting the riff.toml file that exists in the repo. We should either respect an existing riff.toml or merge new properties that are set.
I can "fix" FATS by adding the --handler
flag
Does this mean that riff.toml
is no longer required? Or, is the content just ignored?
Does this mean that riff.toml is no longer required? Or, is the content just ignored?
Both, in effect.
I think we should now consider riff.toml
as something only needed when building locally with --local-path
(and even, we could/should craft that file for the user IMO).
The source of truth is the --xx
flags
it works when supplying --handler option; closing this issue
This output from the logs look suspicious:
The failure is: